this post was submitted on 07 Jul 2025
17 points (87.0% liked)

Selfhosted

49223 readers
448 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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"

you are viewing a single comment's thread
view the rest of the comments
[–] ragingHungryPanda@lemmy.zip 3 points 1 day ago (5 children)

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?

[–] lilcutie24@sh.itjust.works 1 points 1 day ago (3 children)

I used Cloudflare tunnels and YunoHost. It won't connect and it won't listen to any port

[–] 3dcadmin@lemmy.relayeasy.com 1 points 7 hours ago

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

[–] SteveTech@programming.dev 3 points 1 day ago

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.

[–] ragingHungryPanda@lemmy.zip 2 points 1 day ago (1 children)

You're running these commands on the same machine as yunohost, right, not from another computer?

[–] lilcutie24@sh.itjust.works 1 points 23 hours ago

Correct, same computer

load more comments (1 replies)