Error 1033 Cloudflare
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"
Hey bro. I'm just a FNG here, but I've found that the more detail you can give, the better the results (answers) will be. However, two sentences about a Cloudfare error is probably not going to garner much interest. People here I've found, are willing to help, but they can't guess what it is you're talking about.
Kind Regards
Cloudflare won't connect to a port number that high. Drop it down to say 2536 and you will be fine
Failure to connect, still. Odd.
I presume they mean pointing their cloudflare tunnel to direct lemmy.example.com to http://localhost/:[port], and I don't think there's any special rules about that port from cloudflares site.
I use tunnels and ports in about that range for all my sites, and don't have any problems.
It depends... the OP is also using yunohost which can and does have some issues with higher port numbers, plus you also have to factor in if he is self hosting as I suspect, some routers also won't properly forward higher port numbers either. Difficult to say but lowering the port number is one thing to try. Too many variables to really drill down and say what is happening
Wait, failure to connect to local host? That's your own computer, whatever endpoint isn't going through cloud flare. Most apps respond to ports 80/443. You need to either route those to your computer, or in docker route whatever port you want it on to your app. If you have just one app/website, you can do 80/443 universally to the app. If you have more than one, route them to a reverse proxy that can take a domain or sub-domain name and route them to the ports your apps are on.
But yeah, you really need to provide more info.
What's your environment? What's your config, setup, etc?
I used Cloudflare tunnels and YunoHost. It won't connect and it won't listen to any port
Yeah, YunoHost explains why http://localhost:8536/ wouldn't be working. If cloudflared and Lemmy are in separate containers you have to put an actual IP in, since localhost points to the container itself.
Cloudflare and yunohost user here. Need to install the cloudflared service and make sure it runs and the tunnel connects in the zero trust dashboard. Will say healthy when it does. Try a lower port number, something in the 2000-3000 range is good to test. Then in the correct tunnel once it is showing healthy you need to add a public hostname (for ease of use). Say lemmy.mydomain.com, use https then localhost:portnumber/ Then in additional settings you have to turn on notlsverify else it won't work. That should get it working. To be honest I've not bothered setting up various ports other than the defaults so you shouldn't need to set up the port so just try https and localhost and that should do the trick - this could be where you are going wrong as yunohost doesn't explicity need the port setting in most common configurations. Then in the yunohost admin area you can go into applications and open the app and it should work. Any probs give us a shout
Can you access it without Cloudflare?
Does curl http://localhost:8536/ work?
You are using cloudflared right? Because normal (non-cloudflared) Cloudflare doesn't support port 8536.
Are you pointing cloudflare directly to Lemmy? I have mine going from cloudflare to Nginx Proxy Manager configured to serve Lemmy.
There is some additional configuration necessary for a reverse proxy in front of Lemmy, which is potentially where things are getting messed up for you?
Cloudflare tunnels support higher port numbers. I've done it in the past with Portainer. Also Proxmox which listens on 8006. Portainer on 9443.
and... with yunohost in most setups there is no need to use port numbers, for various reasons
It does, but there are issues especially with proxy content. Way easier to listen on lower port numbers especially to debug
I don't doubt that, I'm saying this more because there are additional routes that i had to configure in NPM to get lemmy working properly. This may be where OP is having issues, you can probably set them up in CF too but I have no idea.
I'm gonna try just making it a local instance