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
Alright that makes sense, do you know how to solve that if that webapp is nextcloud aio?
I'm not sure what happened in your setup, but here is how https handling should works:
HTTP_X_FORWARDED_PROTO
header to let the upstream server know that even though the request is over http, the end user actually served over https so it should assume the connection as httpsI think this chain is broken somewhere in your setup and cause nextcloud to not receive the
HTTP_X_FORWARDED_PROTO
header from nginx proxy.I just remember nextcloud has
trusted_proxies
option located inconfig/config.php
file. Not configuring it (or configured it wrong) can cause nextcloud to not trust theHTTP_X_FORWARDED_PROTO
header it received (it assumed to be spoofed).https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html