Precision guesswork here, but I’ve had nginx (not on opnsense) redirecting me to the default host quite a few times recently - all times it was me cocking up its config. It could be that nginx is waiting for the actual target until it times out and then just gives a your opnsense gui as the most reasonable response.
I’d start checking its config. Or pasting it here, after removing secrets, it any.
So I’ve tried spinning up new turnkey containers for nginx to eliminate this as a potential issue. Everything can be accessed internally but new or old config alike, it’s the same inaccessible from WAN issue.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Precision guesswork here, but I’ve had nginx (not on opnsense) redirecting me to the
defaulthost quite a few times recently - all times it was me cocking up its config. It could be that nginx is waiting for the actual target until it times out and then just gives a your opnsense gui as the most reasonable response.I’d start checking its config. Or pasting it here, after removing secrets, it any.
So I’ve tried spinning up new turnkey containers for nginx to eliminate this as a potential issue. Everything can be accessed internally but new or old config alike, it’s the same inaccessible from WAN issue.