Unable to Bind to Endpoint
If FireDaemon Fusion is started when its TCP/IP port is already in use, the start-up will fail and the following error will appear in the FireDaemon Fusion log file located in C:\Program Files\FireDaemon Fusion\logs.
INFO 2025-11-17 11:01:35,006 [06e6c] plugin_server start - Starting server on endpoint 0.0.0.0:443 ERROR 2025-11-17 11:01:35,015 [06e6c] plugin_server start - Unable to bind to endpoint 0.0.0.0:443: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at C:\projects\firedaemon\3rd-party\boost_1_89_0\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'class boost::system::error_code __cdecl boost::asio::detail::win_iocp_socket_service<class boost::asio::ip::tcp>::bind(struct boost::asio::detail::win_iocp_socket_service<class boost::asio::ip::tcp>::implementation_type &,const class boost::asio::ip::basic_endpoint<class boost::asio::ip::tcp> &,class boost::system::error_code &)'] FATAL 2025-11-17 11:01:35,015 [06e6c] pion InitInstance - bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at C:\projects\firedaemon\3rd-party\boost_1_89_0\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'class boost::system::error_code __cdecl boost::asio::detail::win_iocp_socket_service<class boost::asio::ip::tcp>::bind(struct boost::asio::detail::win_iocp_socket_service<class boost::asio::ip::tcp>::implementation_type &,const class boost::asio::ip::basic_endpoint<class boost::asio::ip::tcp> &,class boost::system::error_code &)'] INFO 2025-11-17 11:01:35,016 [02cbc] pion ExitApp - End FireDaemon Fusion
To correct this:
- Open an elevated command prompt
- Change directory to C:\Program Files\FireDaemon Fusion\configuration
- Edit the file called fusionservices.xml
- Change the value of the <Port> element to the correct port (e.g. 20604) and save the file
- Start the FireDaemon Fusion service:
net start "firedaemon fusion" - Point your browser at FireDaemon Fusion and login: https://localhost:20604
Wrong or Missing SSL/TLS Certificate Passphrase
FireDaemon Fusion validates the SSL/TLS private key certificate passphrase. You will not be able to apply an invalid passphrase. If you find that FireDaemon Fusion does not start due to a certificate failure, the simplest thing to do is:
- Open an elevated command prompt
- Change directory to C:\Program Files\FireDaemon Fusion\configuration
- Edit the file called fusionservices.xml
- Change the value of the <SSL enabled="1"> attribute to "0" and save the file
- Start the FireDaemon Fusion service: net start "firedaemon fusion"
- Point your browser at FireDaemon Fusion using HTTP (i.e. NOT HTTPS) and login: http://localhost:20604
- Go to Global Options
- Check "Use SSL/TLS"
- Reconfigure your CA Bundle, Certificate, Private Key, and Passphrase
- At an elevated command prompt restart the FireDaemon Fusion service:
net stop "firedaemon fusion" && net start "firedaemon fusion" - Point your browser at FireDaemon Fusion: https://localhost:20604
