503 error on neo4j ec2 instance - amazon-ec2

I have installed neo4j on an aws ec2 ubuntu instance and changed the password. From a remote machine I can
rhys#coconut:~$ curl -u neo4j:password http://ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:7474
{
"management" : "http://ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:7474/db/manage/",
"data" : "http://ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:7474/db/data/"
}
Going to
http://ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:7474/db/data/ with dbms.security.auth_enabled=false produces a 503 error;
HTTP ERROR: 503
Problem accessing /browser/. Reason:
Service Unavailable
Powered by Jetty://
How can I access the neo4j browser securely and without getting a 503 error?

Remote access to the browser is disabled by default.
Make sure to uncomment the following line in your neo4j-server.properties file :
org.neo4j.server.webserver.address=0.0.0.0

Related

Failed to build apache kudu because unable to connect to service.gradle.org

When trying to build kudu in my ec2, I got an error "HTTP/1.1 403 Forbidden". My connection was opened through a proxy. The domain that we are trying to connect to here is "service .gradle.org". This can be accessed through HTTPS. Here the build is run using the gradle wrapper jar (v6.8.3). Here, a 403 Forbidden error of the above type kept appearing. It lookes like the connection is trying to use HTTP instead of HTTPS.
This problem is not occurring when the build is run in an environment without a proxy
Build fail image

websocket._exceptions.WebSocketProxyException: failed CONNECT via proxy status: 403 when running in python anywhere

When trying to run my .py script it's showing the error
websocket._exceptions.WebSocketProxyException: failed CONNECT via proxy status: 403
I am using a module tvdatafeed which uses websocket. Please help to solve the issue. So that I can test my script on cloud
Free accounts cannot connect out to websocket endpoints.

Facing this error when i upload laraval app to live server

This error occur when i trying to hit api from live server.But locally api running correctly. I got this error
cURL error 28: Failed to connect to testapi.certccie.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Here we uploaded error image
https://i.stack.imgur.com/MKUZn.png
Maybe this is because of your host that your host dont access to certccie.com.
Try on another host.

Laravel Dusk Testing has an error on the server Curl error thrown for http POST to /session with params

I would like to ask me to try the following instructions on Plesk Server:
php artisan dusk
The following error will occur:
1) Tests\Browser\ExampleTest::testBasicExample
Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY","chromeOptions":{"binary" :".\/vendor\/laravel\/dusk\/bin\/chromedriver-linux","args":["--disable-gpu","--headless","--no-sandbox"," --verbose","--window-size=1024,768"]}}}
Failed connect to localhost:9515; Connection refused
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:292
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:126
/var/www/vhosts/fanswoo.com/fanswoo-framework/tests/DuskTestCase.php:43
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:192
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/framework/src/Illuminate/Support/helpers.php:754
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php: 193
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:93
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:64
/var/www/vhosts/fanswoo.com/fanswoo-framework/tests/Browser/ExampleTest.php:22
I suspected that the Chrome Driver could not be executed, so I used the following command to detect:
./vendor/laravel/dusk/bin/chromedriver-linux
The return is as follows:
Starting ChromeDriver 2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d) on port 9515
Only local connections are allowed.
Indicates that ChromeDriver can be opened normally.
The code can also be detected on the local computer. Only when the dusk command is executed in Plesk Server will the error occur. May I ask what God should I continue to do or what to modify? Thank you!
The server specifications are as follows:
CentOS 7.5
PHP 7.1
DB SQLite3
Laravel Version 5.7
ChromeDriver Version 69
If you able to start chromedriver successfully, now try to access the below url with respective port.
http://localhost:{port}/status
For e.g., in above message, the server started on port 9515. Access the url in browser, http://localhost:9515/status
You should get above message indicating server is accessible with hostname as localhost
If your are not able access, then fix the specific issue

Docker For Mac / Lando: cannot cURL external webservice

I am testing out Lando for a new local dev setup.
Everything has gone well so far but I am running into an error that I don't get on my old Vagrant/VM environment, but do with Lando.
We have part of the site that uses Guzzle to fetch data from a web service. On Lando, I get a cURL error:
cURL error 7: Failed to connect to webservice.internalsite.com port 80: No route to host
How can I resolve this? When I try to ping that url, it says "Destination host unreachable". I am using Docker For Mac if that factors in.

Resources