I don’t know what to do, I’m experimenting with creating a Lemmy instance. it’s listening on port 8536 but cloudflare won’t respond and connect and while i connected the tunnel to the instance, i can’t figure out the error or how to make it connect to the server.
“Failed to connect to localhost port 8536 after 0 ms: Couldn’t connect to server”
Yeah, I feel like we’re missing some info here.
I have to admit that I have no experience with yuno. Always seemed interesting, but not like something that fits into my work flow.
If they’re self-hosting at home (which I’m also doing for some services), I’d presume they’re probably running their stuff on a single machine, so I’m not sure where their router would come Into it. The data the cloudflare tunnel process receives should look the same to the router no matter the port it is ultimately sent to, and when it is sent to an address internal to the machine, shouldn’t pass through the router again.
It should, and yes I used to think that. I’m in the UK and some routers just fail to work properly with higher port numbers, especially cheap routers from cheaper providers. Once you start getting above 8000 the traffic is limited thus me saying try a lower port number. Plus yunohost doesn’t really ask for a port number as you should add a domain first, then install the application (it uses docker btw) on that domain, then cloudflare to the domain. So the port number isn’t required. I’m guessing, but can’t be sure, that this is the real issue. yunohost adds a self signed cert and configures the firewall etc. so if you don’t do it right using a cloudflare tunnel it just doesn’t work. I’m guessing the OP hasn’t done it like this, and then it will never work - believe me I’ve tried. yunohost also adds fail2ban, firewall inside yunohost and various other ways to protect what is served