I use a reverse proxy so I still use DNS name to access internally.
this post was submitted on 04 Jul 2023
21 points (95.7% liked)
Selfhosted
40407 readers
210 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
This is the way
I believe some things are populated by your hostname in the lemmy configs so straight IP may break a few things.
I had the same issue as OP when setting up my instance. Properly setting the domain name in all the config files fixed it for me. So I am assuming you are right.
When you say internally, do you mean behind a NAT, or something to that effect?
I mean from the same LAN.
You’ll probably want to do it by dns name
It worked on 0.17.4, but on 0.18.0 I get the error you get