Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Autostart after boot failing
#2
The error "socket.error: No socket could be created" indicates that there is already something using the default port (port 80).

Do you have another server program like apache running?

Once you get SIP to start you can change the port it uses from the Options page. Change "HTTP port:" from 80 to something like 8080. This may help.
You will then need to add the port to the URL when you access SIP for example http://x.x.x.x:8080

I have seen this happen after starting SIP manually and then trying to start it using systemctl.
Reply


Messages In This Thread
Autostart after boot failing - by Gazmac52 - 2019 Apr 12, 11:20 PM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 12:38 AM
RE: Autostart after boot failing - by Gazmac52 - 2019 Apr 13, 12:54 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:04 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:09 AM
RE: Autostart after boot failing - by Gazmac52 - 2019 Apr 13, 01:10 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:45 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)