OPNsense Forum

English Forums => Web Proxy Filtering and Caching => Topic started by: bignick8t3 on January 18, 2019, 05:16:01 pm

Title: HA Proxy Config
Post by: bignick8t3 on January 18, 2019, 05:16:01 pm
Hello All,

I'm currently migrating from pfsense to opnsense and for the majority this has been fairly pain free as I've been configuring opnsense while using pfsense.

My last bit to do is HA Proxy to which I'm using as a reverse proxy with SSL offloading, the how to looks similar to that of the package used by pfsense but it looks like HA Proxy in opnsense has seen some significant updates since the documentation.

Is there anyway that I can take my config file from pfsense and load this into opnsense as it would save me a good bit of time.

Many thanks

Nick
Title: Re: HA Proxy Config
Post by: fabian on January 18, 2019, 05:31:41 pm
My last bit to do is HA Proxy to which I'm using as a reverse proxy with SSL offloading, the how to looks similar to that of the package used by pfsense but it looks like HA Proxy in opnsense has seen some significant updates since the documentation.

The docs are for 1.6 so they are a bit outdated. The forms are similar (contain at least the same properties if not more) and the menus have been renamed and contain some documentation. It still helps but yes, this docs page needs some maintenance.

Is there anyway that I can take my config file from pfsense and load this into opnsense as it would save me a good bit of time.

For some "legacy" core components yes, but for sure not for OPNsense native plugins (those with /ui in the URL) and core functionality (which may provide a migration but not sure if it works because that depends on the version you are using).

For example, the load balancers haproxy, nginx and relayd are OPNsense native plugins.
Title: Re: HA Proxy Config
Post by: bignick8t3 on January 18, 2019, 06:01:24 pm
Many thanks for your response.

No matter that I cannot import config from elsewhere as the intros for each section do a good job of explaining their uses/requirements.

I'm sure I'll muddle through and get it all up and running.

Thanks again,

Nick