ArangoDB Web Interface Log doesn't work, [Error] Failed to load resource: the server responded with a status of 404 (Not Found) - arangodb

Just installed ArangoDB on Mac Mojave, works great, but I can't get the Logs Tab in the Web Interface to work. Get a [Error] Failed to load resource: the server responded with a status of 404 (Not Found)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found)
ReferenceError: Can't find variable: entries

Related

why i got this Error: Failed to load resource: the server responded with a status of 403 (Forbidden)

I tried many times but can't solve this error I checked server side there are all okay but got this error

Is Adblock filtering my website?

How can I bypass it ? It has 'ad' on its hostname, I think this is the reason.
http://testinad.info
Every resources are blocked. It is completely unviewable by everyone running adblock. Is there anything to do in my code ? Or where to get it deblacklisted ?
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/css/style.css Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/img/logo.svg Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/img/webicon-facebook.svg Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/img/webicon-googleplus.svg Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/img/webicon-twitter.svg Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
http://testinad.info/assets/img/logo.svg Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
Because of the following filter
/inad.
Found in: EasyList
It's a filter in EasyList.

500 internal server error on gitlab

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster#gitlab.dev.sample.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.0-fips DAV/2 Phusion_Passenger/4.0.42 mod_bwlimited/1.4 mod_fcgid/2.3.9 Server at gitlab.dev.sample.com Port 80

Could not retrieve catalog from remote server: Error 400 on SERVER: Error 403 on SERVER: Forbidden request:

I am trying to follow the documentation at this link:
http://docs.puppetlabs.com/pe/latest/quick_start.html
When I get to the part where one runs ...
sudo puppet agent --test
I get this error message ...
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Error 403 on SERVER: Forbidden request: red-cricket-pe-master (xxx.xxx.xxx.xx) access to /facts/red-cricket-agent [save] authenticated at line 45
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Thanks
Red
Found my answer here: https://serverfault.com/questions/491623/puppet-enterprise-2-7-error-400-on-server-error-403-on-server-cant-puppet/493085#493085
Looks like you HAVE TO install the console.

Nginx sends status 200 after PHP parse error

I've configured nginx with php-fpm on Ubuntu (and everything works pretty well).
One thing I encountered is that HTTP status code 200 is sent, when a PHP parse error occurs. The error log contains the following entry:
[error] 3205#0: *2854 FastCGI sent in stderr: "PHP Parse error: syntax error, unexpected T_REQUIRE_ONCE in /var/www/.../index.php on line 32" while reading response header from upstream, client: 1.2.3.4, server: example.com; request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "example.com"
I was not able to figure out, why not a code 50x is sent. I have not configured any error_page settings and I read the documentation of error_page. I also tried it to set the status code (with error_page 500 =500 /50x.html and so on). But always status 200 is returned.
I can send status headers from PHP (header('HTTP/1.1 404 Not Found')), this works. However, for errors issued by the PHP interpreter (also uncaught exceptions), the server's response doesn't take into account that an error occurred.
FYI, this is now fixed in Xdebug (2.2) for PHP 5.4 and up. Sadly, it needed a change in PHP to make it work that could not be back-ported to 5.3.

Resources