Subdomain port redirects

Hello, my registrar is Namecheap, and I moved DNS over to CloudFlare recently. Also have DDNS at No-IP.

I had redirects (I believe called Aliases there) setup at Namecheap to point to my :, but I can’t seem to figure out where I can do that here. Only things I saw looking around that might be close were Page Rules or Spectrum…

The strange thing to me is that 2 are still working but 2 aren’t working.
So, yeah I don’t really understand how there are 2 working in the first place since I didn’t set anything up. I know when I transferred DNS it automatically pulled some records over that I had, but I can’t see the details of them, it’s just Type, Name, Proxied IP and that’s it.

I’m obviously missing something or not understanding something here.

Cloudflare only supports certain ports

Nothing else can be proxied.

Post the exact URL for more details.

I did see that article earlier, which confused me a bit more because 1 of the redirects that is working is this:

goes to DDNS:44444

is supposed to go to DDNS:8080 but doesn’t

If I can’t proxy, where can I add redirects to specific ports?

8080 will work via the proxies, however only via HTTP and not HTTPS.

Do you plan to use HTTP on that address with port 8080?

Again, whats the URL?

I had vgm.evermore.pro redirected to that before, but that’s one that stopped working. It is just HTTP

That URL does not point to Cloudflare.

Also, nothing is responding on port 8080 at that IP address anyhow.

You must have mixed something up, I am afraid.

vgm.evermore.pro does point to Cloudflare and it does respond, so it probably does not point to aforementioned IP address, as there is no response from it itself.

Anyhow, http://vgm.evermore.pro:8080 does work right now.

Yeah, vgm.evermore.pro:8080 does work.
So is there no way to just say sub-domain.evermore.pro points to host:port?

There is a way, but you need an SRV record for that and your client software will need to support it. Does it do that?

Oh, ok. I’m not sure that it does support that, I’d have to look into it more. That gets me pointed in the right direction though.

Thanks for your assistance

Assuming we are talking about regular web browser, what else you could do is use a page rule to redirect requests to standard ports such as 80 and 443 to 8080. But that will be a typical redirect and the port will naturally show up.

That’s actually the first thing I tried, but I wasn’t expecting to have to type in the port in the browser so it wasn’t working

If you have a redirect on standard ports, you wont have to type the port.

This topic was automatically closed after 31 days. New replies are no longer allowed.