On Friday, 5 January 2018 at 16:47:53 UTC, Steven Schveighoffer
wrote:
On 1/5/18 11:30 AM, Martin Tschierschke wrote:
Hello,
when starting my vibe.d service I get the message of failed
address binding:
Failed to listen on 127.0.0.1:8030
Failed to listen on 10.0.0.1:8030
object.Exception@../../.dub/packages/vibe-d-0.8.2-rc.2/vibe-d/http/vibe/http/server.d(2035):
Failed to listen for incoming HTTP connections on any of the supplied
interfaces.
It's attempting to listen on localhost:8030, and 10.0.0.1:8030,
but can't bind to either address. Then it looks like you get an
exception. Does it actually continue running?
That error is always there, don't worry about it OP. The issue
you are having doesn't have anything to do with the binding,
after all you get a 400 error from the server.
But with Firefox http://10.0.0.1:8030
gives the long Error:
400 - Bad Request
Bad Request
Internal error information:
object.Exception@../../.dub/packages/vibe-d-0.8.2-rc.2/vibe-d/stream/vibe/stream/operations.d(363):
Reached maximum number of bytes while searching for end marker.
----------------
....
truncated
.....
../../.dub/packages/vibe-d-0.8.2-rc.2/vibe-d/core/vibe/core/core.d:1269 void
vibe.core.core.CoreTask.run() [0x94574a]
??:? void core.thread.Fiber.run() [0xa3c7ff]
??:? fiber_entryPoint [0xa3c562]
??:? [0xffffffff]
This looks like a real error that isn't related to the bindings
(as long as it's not some weird stale server). I'd suggest
trying to create a minimal example and post it to vibe.d's
issue tracker.
Also try checking the developer tools of both browsers to see
what headers they are sending, vibe.d probably has a problem with
one of those and breaks because of it. But to be sure for sure
you need to provide a code example.
