when installing laravel, there's an error
Failed to decode response: zlib_decode(): data error
Retrying with degraded mode, check https://getcomposer.org/doc/articles/troubleshooting.md#degraded-mode for more info
what cause this error
Well according to the link that you posted:
-Disable HTTP-scanner if you use ESET antivirus
-Disable your ipv6 connection
Related
We are trying to get elastic-apm install (for now on our development systems).
According to Homebrew, we have the latest elasticsearch-oss (7.10.2), kibana-oss (7.10.2) and today installed apm-server-oss (which is at version 7.13.0).
Running a apm-server test output we get:
% apm-server test output
elasticsearch: http://localhost:9200...
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: ::1, 127.0.0.1
dial up... OK
TLS... WARN secure connection disabled
talk to server... ERROR Connection marked as failed because the onConnect callback failed: could not connect to a compatible version of Elasticsearch: 400 Bad Request: {"error":{"root_cause":[{"type":"invalid_index_name_exception","reason":"Invalid index name [_license], must not start with '_'.","index_uuid":"_na_","index":"_license"}],"type":"invalid_index_name_exception","reason":"Invalid index name [_license], must not start with '_'.","index_uuid":"_na_","index":"_license"},"status":400}
Because the documentation on getting APM going is somewhat obtuse, perhaps this is a configuration issue. But how to investigate further?
Is the solution to install an earlier version of apm-server? If so....how to actually do that with homebrew?
I had the same issue when using non-oss versions. Managed to fix this by upgrading ElasticSearch and Kibana to 7.13.2.
I was implementing laravel websockets package in project it is working fine in my local machine but on server first it was giving error of Connection timeout That problem was solved when add TCP port in aws security group but after that it starts giving new error
WebSocket connection to 'ws://52.64.101.38:6001/app/ABCDEF?protocol=7&client=js&version=4.3.1&flash=false' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
Here are errors I am getting in console when try to connect websocket server
I was searching about this error i found this github thread . Which is saying try to bound with 0.0.0.0 but I dont know what does it means,
https://github.com/GeniusesOfSymfony/WebSocketBundle/issues/251
I was also getting this error on local machine but was later resolved when i downgrade package version 1.6
NOTE: I am using ubuntu server aws services
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
I've installed pgAdmin4 v2 on Windows 7. The installation went fine and I could launch it successfully without any issue. After couple of days, now if I try to load GUI I am getting the error – “pgAdmin 4 Desktop Runtime has stopped working”. Log file shows below error entries:
raise URLError(err)
URLError: <urlopen error Tunnel connection failed: 407 authenticationrequired>
2018-03-26 13:16:01,937: ERROR pgadmin: Exception when checking for update
Does anyone know how to fix the issue?
Version check was root cause of the problem as my network has restricted access. Disabling version check in application config settings (UPGRADE_CHECK_ENABLED = False in config_local.py) fixed the issue in my case.
I am using ispconfig, and I have created a FTP user with the respective password. But when I try to connect to that server I hm experiencing this error.
Error: Authentication failed.
Error: Critical error
Error: Could not connect to server
I tried all the solutions given Here, but to no avail.
So I found the error,
I had used FileZilla to login into the server for uploading some file, and the connection was using the sftp:// protocol.
When I tried to conenct with the ftp account the above error was being reported, even after I updated/confirmed the user password.
Finally I realized that the protocol was wrong and after removing the sftp:// protocol prefix, it defaulted to ftp:// which the server readily accepted.