I currently have Nginx Proxy Manager running through portainer in a VM on my truenas server but I’d like to have it running directly on my opnsense router.
I tried to get it running before I set it up in docker but I couldn’t manage to get the Nginx plugin working properly. Is there an Nginx plug-in available for opnsense that has the same web front end?
I recommend you serve whatever you want to serving on vm’s/whatever on your internal network, and then use HAProxy (Built-in) to do the forwarding via opnsense. HAProxy is a High Availability and Performance proxy and load balancer, it does what nginx proxy manager does and more.
The same front end? Nah it has it’s own menus and such. If you’re familiar with the anatomy of the conf files you can piece each sub-menu within the plugin to it’s corresponding section in the conf. Not everything that I need was represented. There is a way to inject custom blocks, but it’s pretty cumbersome.
Honestly? I’m considering going back to a dedicated nginx host for two reasons. Firstly it’s just easier to configure. Secondly, I’m sending internal traffic to the public DNS addresses for some of the services and I’m not 100% positive those fuck-heads over at Comcast aren’t charging me for the hairpin route. If I had a local, internal proxy, I could avoid that.
The only reason I want it on the router is if either my vm or my server go down for whatever reason I have no access. My router is way overkill hardware wise (it’s running opnsense and Adblocking and I’ve never seen above 2%) cpu usage.
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).
I replied to a nginx plugin question years ago on Reddit. Simple fact is, the plugin is really just designed to host a simple-ish webpage. https://www.reddit.com/r/OPNsenseFirewall/comments/klauwb/setting_up_a_web_server_on_my_opnsense_box_with/
I recommend you serve whatever you want to serving on vm’s/whatever on your internal network, and then use HAProxy (Built-in) to do the forwarding via opnsense. HAProxy is a High Availability and Performance proxy and load balancer, it does what nginx proxy manager does and more.
The same front end? Nah it has it’s own menus and such. If you’re familiar with the anatomy of the conf files you can piece each sub-menu within the plugin to it’s corresponding section in the conf. Not everything that I need was represented. There is a way to inject custom blocks, but it’s pretty cumbersome.
Honestly? I’m considering going back to a dedicated nginx host for two reasons. Firstly it’s just easier to configure. Secondly, I’m sending internal traffic to the public DNS addresses for some of the services and I’m not 100% positive those fuck-heads over at Comcast aren’t charging me for the hairpin route. If I had a local, internal proxy, I could avoid that.
The only reason I want it on the router is if either my vm or my server go down for whatever reason I have no access. My router is way overkill hardware wise (it’s running opnsense and Adblocking and I’ve never seen above 2%) cpu usage.