socket.error...but changing port didn't help, nor did reboot
|
socket.error...but changing port didn't help, nor did reboot
|
2020 Jul 13, 02:34 PM
(2020 Jul 12, 08:05 PM)dan Wrote: Usually the "No socket could be created" error indicates that something else is using the port. "Cannot assign requested address" could also be that not only the port is configured but also the IP address. When the IP of the PI changes e.g. by DHCP than there is trouble. Unless you have multiple interfaces you would configure the ip as 0.0.0.0 --Gerard |
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
socket.error...but changing port didn't help, nor did reboot - by noequus - 2020 Jul 12, 01:10 AM
RE: socket.error...but changing port didn't help, nor did reboot - by dan - 2020 Jul 12, 08:05 PM
RE: socket.error...but changing port didn't help, nor did reboot - by astrogerard - 2020 Jul 13, 02:34 PM
RE: socket.error...but changing port didn't help, nor did reboot - by noequus - 2022 Aug 13, 11:34 PM
RE: socket.error...but changing port didn't help, nor did reboot - by astrogerard - 2022 Aug 14, 06:35 PM
RE: socket.error...but changing port didn't help, nor did reboot - by noequus - 2022 Aug 15, 05:31 AM
|
