Chrome 55 was notorious for
net::ERR_INVALID_HTTP_RESPONSE, when using custom ports outside of
443. This affected thousands of servers but notably Shoutcast Version 1 and 2.
A simple fix may just be to use
8080 instead of
9300 as it can coexist with 80. But your issue here is your browser, not your server or hardware. The real fix is to update your browser to a version that is considered stable and up to date.
Google released a build that fixed this very issue after many complaints. Considering that we are now in version 59 stable and 60 stable development, you should update your Chrome to resolve this issue, after all that's why we get new versions of browsers all the time to fix issues, sometimes new fixes break things etc.
Your server is not serving CSS or JS correctly, and possibly other server-side resources. This is actually reported in the Firefox console.
Doing a curl on a element or page should look something like this:
HTTP/1.1 200 OK
Date: Tue, 01 Aug 2017 15:36:05 GMT
Set-Cookie: __cfduid=d01134b2133a3b0424baada976e2258ff1501601765; expires=Wed, 01-Aug-18 15:36:05 GMT; path=/; domain=.bybe.net; HttpOnly
Last-Modified: Fri, 07 Apr 2017 14:51:08 GMT
Expires: Tue, 01 Aug 2017 19:36:05 GMT
Cache-Control: public, max-age=14400
Doing a CURL on your resources returns this:
The code above is not valid and should not work at all. The reason that FireFox is working while Chrome is not is because Chrome is more strict when it comes to security concerns.
Doing a CURL on your pages returns:
HTTP/1.0 200 OKAY
To replicate this issue, you can do a online test yourself using online CURL. To add your username and password, click
+ Add Option, find
user -u and click it, then Insert Attributes as
So, the solution to all your problems is to fix your web server serving all files and pages correctly.