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
It looks like this is a discrepancy between the default approach to listen on ::1 and 0.0.0.0 and the system's network configuration, where ::1 probably implicitly also handles IPv4 traffic. Unfortunately there are also systems where you need to listen on both separately, so it's not really possible to implement a fits-all solution. For real-world applications, this will have to be made configurable.
Which is strange because there is nothing listening on IPv4 on port 1337.
If I set bindAddresses to 127.0.0.1 or even 0.0.0.0 it works, as expected.
The text was updated successfully, but these errors were encountered: