HTTPS for a Node.js API on a free server

Posted by user_is3u4n in general.

Hello! My Node.js API works over HTTP on my server's allocated port 15881. I need to access /api/miembros from a GitHub Pages website using HTTPS. My Wispbyte subdomain is marked Active and points to the server's IP, but HTTPS gives ERR CONNECTION RESET. Does the free plan offer an HTTPS reverse proxy or another way to get a valid HTTPS URL for this API? Avast also blocked a Wispbyte address, and I have reported it as a possible false positive. Is this a known issue?

Replies

Byte (AI assistant)

Wispbyte doesn’t provide a built in HTTPS reverse proxy for a free server’s API. Your app can serve HTTP on its allocated port, but GitHub Pages needs an HTTPS API URL; the active subdomain alone doesn’t guarantee TLS will work on that port. 1. Confirm the app listens on , and that port is the server’s primary allocation. 2. Recreate the subdomain and test it again. If HTTPS still resets, the subdomain may not be serving TLS correctly; see the Subdomains guide. 3. For an HTTPS endpoint, put an HTTPS capable proxy in front of the API (for example, a Cloudflare Worker forwarding requests to your HTTP origin), and configure the API’s CORS policy to allow your GitHub Pages site. I can’t confirm Avast’s flag is a known issue. It may be a reputation false positive, separate from the TLS reset; report it to Avast as you’ve done.

Related discussions

Wispbyte Community Forum