222
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jun 2023
222 points (100.0% liked)
Selfhosted
40670 readers
341 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Hi @ubergeek77@lemmy.ubergeek77.chat
I must be doing something wrong here because unlike many others I can't seem to get this working! Please can you offer some advice?
I have amended the config.env file to change the HOSTNAME, SITE NAME and ADMIN USER but left everything else the same.
I then ran ./deploy.sh and everything seems to have worked because it presented me with the admin login credentials and basic instructions to shutdown and start the instance. I tried simply typing the IP address of the docker container in to a browser but that didn't work and TBH I didn't expect it to. I then typed the URL into the browser and I'm getting a "ERR_TOO_MANY_REDIRECTS" error message. I read through the trouble shooting on your Github but the only reference to too many redirects mentions a Cloudflare API token, I'm not using Cloudflare nut I am using nginx proxy manager to point my URL to the docker container.
I hope some of this makes sense.
Hey there, please note that running behind a reverse proxy is not supported. You can do it if you want, but you are kinda on your own, sorry.
If it helps, you will probably need to disable Caddy's TLS in the config, and you will need to make sure that the request reaches Caddy via the correct host. You can't reverse proxy directly to port 80 over an IP, it needs to think it's coming from an actual domain.
You can also check out my advanced configuration page to learn how to override the Caddyfile template and roll your own config that is more compatible for your use case.
Good luck!
Thank you so much for replying.
I think this is above my skill level, but I will have a read through your advanced configuration page and see if I can understand it.
Thanks again, but I think I'm going to need more than luck!! LOL
You're welcome!
If you're not already, I recommend trying to host this on a cloud VPS service, such as Vultr, Linode, or DigitalOcean. This would give you a reliable, always online Lemmy instance, which means you won't miss any federation data. Even a cheap $5 VPS instance would be enough to get you started, though a $10 would give you more breathing room.
If you're hosting at home, it's generally not a good idea to do that, especially for an application like Lemmy. Most consumer grade network equipment at home might not be equipped to deal with the unrelenting 24/7 flood of data coming in due to federation. And if your power or internet ever goes out, you will be missing any comments, posts, or votes that were sent out during your downtime.
Thank you again. Yeah, I'm trying this from home as opposed to a vps. It's more as a learning exercise than a serious instance.
I'm still going to try and getting it working behind my reverse proxy, like I say, as a learning experience.