You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HTTP server is being started with 0.0.0.0:50509 as shown in the logs:
INFO freenet::server: HTTP gateway listening on 0.0.0.0:50509
When the server checks if the connection is local, it's using the binding address (0.0.0.0) rather than the incoming connection address to determine if it's a loopback connection. Since 0.0.0.0 is not a loopback
address, the check fails.
The workaround is to call freenet with the parameter --ws-api-address 127.0.0.1.
The proper fix is to modify the code to check the incoming connection address rather than the binding address.
The text was updated successfully, but these errors were encountered:
The HTTP server is being started with 0.0.0.0:50509 as shown in the logs:
INFO freenet::server: HTTP gateway listening on 0.0.0.0:50509
When the server checks if the connection is local, it's using the binding address (0.0.0.0) rather than the incoming connection address to determine if it's a loopback connection. Since 0.0.0.0 is not a loopback
address, the check fails.
The workaround is to call freenet with the parameter
--ws-api-address 127.0.0.1
.The proper fix is to modify the code to check the incoming connection address rather than the binding address.
The text was updated successfully, but these errors were encountered: