Selfhosted
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!
view the rest of the comments
Whats wrong with NPM?
I mean, use what you want. But caddy is significantly easier to configure. It additionally handles SSL and protects your proxy targets with zero configuration (by default) and supports live configuration reload via the admin interface. It's tits.
Here's my config: http://i.xno.dev/u/fc8N0n.png
Caddy is running a wildcard SSL cert, so once I've connected my box to cloudflare, I can setup a subdomain by simply adding it to my caddy config. No additional setup is required. It also works directly with docker, so if you install the
lemmy(name of the container) docker container, you can reverse_proxy by simply (assuming they're on the same docker network):That sounds more or less to be exactly what I'm doing with NPM currently. I don't see how it's easier to configure as all I did was fire up the NPM container, log in, and add my host targets.
NPM also handles SSL both standard http verification as well as DNS auth for wildcards.
Caddy can do the same and there is a steep learning curve but I switched about a year ago and only need to touch the config file when I add a host. Can even bring that config to a new server and it will stand up once it starts and picks up the config.
I'd be happy to switch if I had a good tutorial for caddy. Unfortunately I couldn't find one.
How complex is your nginx reverse proxy? Caddy is relatively straight forward: https://i.xno.dev/u/fc8N0n.png
It doesn't work. I can't manage to debug it.
Fedora server. Podman. Selinux. Port 8443. Ipv4.
...what exactly doesn't work. You're not really giving me enough to help you with.
Thx for offering your help.
If I would know, I could debug it, but I don't know where the problem is. I assume the problem is somewhere with podman or selinux
But you gotta understand, there's no subject to your statement. You just said "it doesn't work" and I have no idea what you're doing. Are you installing podman? Are you installing caddy? Are you setting up caddy as a reverse proxy? Are you trying to bring your dog back from the dead? I have no frame of reference.
Sorry for not having expressed what I did. I wrote a podman compose file, pulled the caddy image, wrote a caddyfile, started it and tried to connect to a service via subdomain.domain.tld .
The caddyfile contains my http and tls ports and the domain and ip for the reverse proxy routing according to the docs.
The result is no log entry in caddy and no result in the browser or curl.
You'll probably get better help if you post your config and any logs. Caddy may not log an entry to a file but you can watch the console logs to see everything (
podman logs caddyor similar.)Thanks. For now, I spend too much time with it. I'll try some other time again.
Did you setup DNS to point to your caddy sever?
Yes, it works with nginxproxymanager. There's probably something going on with selinux - I may disable it the next time to test the assumption.
Is your caddy container network set to host? Or at least set to a network which is on the same network as your proxied services?
Ensure that nginx is stopped, and if the domain doesn't work, attempt to direct connect using your servers IP address and the correct port. If you still can't connect, check your firewall rules.
Thx, thats not it