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

Selfhosted

49223 readers
560 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
[–] VeganCheesecake@lemmy.blahaj.zone 1 points 10 hours ago* (last edited 10 hours ago)

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.