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"
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.
-
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.
Cloudflared, yes. "curl: (7) Failed to connect to localhost port 8536 after 0 ms: Couldn't connect to server"
-
Cloudflared, yes. "curl: (7) Failed to connect to localhost port 8536 after 0 ms: Couldn't connect to server"
What's the URL you using to access it without Cloudflare?
Edit: Also that curl tells me it's not listening on that IP/port.
-
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"
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 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"
Cloudflare won't connect to a port number that high. Drop it down to say 2536 and you will be fine
-
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.
-
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
-
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"
I'm gonna try just making it a local instance
-
What's the URL you using to access it without Cloudflare?
Edit: Also that curl tells me it's not listening on that IP/port.
To add: (I'm just going down the checklist here https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/)
- Can you show us that cloudflared is actually running. I wanna see it
- Does your firewall allow the connection
Here's the troubleshooting page
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/-
Have you gotten to the authentication step?
-
What do the logs say?
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/diag-logs/
-
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. -
I used Cloudflare tunnels and YunoHost. It won't connect and it won't listen to any port
You're running these commands on the same machine as yunohost, right, not from another computer?
-
You're running these commands on the same machine as yunohost, right, not from another computer?
Correct, same computer
-
I used Cloudflare tunnels and YunoHost. It won't connect and it won't listen to any port
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
-
Cloudflare won't connect to a port number that high. Drop it down to say 2536 and you will be fine
wrote last edited by [email protected]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.