Closed wesleylc1 closed 4 years ago
Really should be asking this question on the pfSense forum.. But anyhow.. did you spot the difference?:
I'm sorry for posting this content here on GitHub !! I posted the problem on the pfsense forum, but I haven't had help there yet.
I'm so sorry.
After adjusting the frontend, according to your observation, it works, but I still have problems accessing the web server externally. It does not access via smartphone (Firefox / Chrome), unless the https protocol is indicated (https: / /nextcloud.projectus.com.br), and on desktops it is necessary to indicate https: // only when connected by Google Chrome.
note: The problem does not occur when connecting using the wan-ip interface that was previously configured, this problem only occurs when publishing to connect via the new ISP.
Hey, @PiBa-NL
I hope everyone is okay!
I have a multi-wan HAproxy environment, with different incoming SIP traffic, responding on two front ends on ports 80 and 443, in which traffic is successfully directed to all back ends.
But my problem starts now, at the moment when I need to add a third front-end, a new ISP for HAProxy, and direct traffic from a Backend to this new WAN-ip.
Here I can explain in more detail the steps taken in the settings:
Finally, I published the new wan-ip address in the external DNS, but the web server is not accessible.
With kind regards!