Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Alert/Warning Questions / Cannot Bind To Socket

    Scheduled Pinned Locked Moved Cache/Proxy
    1 Posts 1 Posters 238 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      ccoggins
      last edited by

      Hello Everyone,

      I have two pfSense servers for failover/load balancing.
      On my one server, I have been able to get my 2019AppService1 frontend to start, but on this other instance of pfSense I cannot get it to start.

      "[ALERT] 030/084434 (58050) : Starting frontend 2019AppService1: cannot bind socket [12.174.50.4:2506]"

      This is a brand new IP address that we have not used for anything yet.

      I also have a second question about warnings/alerts.
      "parsing [/var/etc/haproxy_test/haproxy.cfg:1505] : 'use-server' expects a server name."

      Do I just go to the folder and open haproxy.cfg and go to line 1505 to see where this error is occurring or is there some sort of log I should be looking at to figure out what is going on with these warnings?
      We updated pfSense back in October and this is the first time I have been in HAProxy and I am seeing a bunch of warnings that are not related to what I have been trying to set up, but items that were set up years ago.

      Thank you!

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.