Facing this error when i upload laraval app to live server - laravel

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.

Related

WebSocket connection to 'protocol=7&client=js&version=4.3.1&flash=false' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

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

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.

Can not connect to AWS parse server on Mac : ssh_exchange_identification: Connection closed by remote host

The image from my terminal
Hi, I am following a Swift Xcode class, and now we are building a project required to connect with AWS parse server, After tried lots of times, it still the same error: ssh_exchange_identification: Connection closed by remote host
Here is the error message:
luodeMacBook-Air:desktop luo$ chmod 400 onepicioskeypair.pem luodeMacBook-Air:desktop luo$ ssh -i "onepicioskeypair.pem" ubuntu#ec2-18-216-187-86.us-east-2.compute.amazonaws.com ssh_exchange_identification: read: Operation timed out luodeMacBook-Air:desktop luo$
Please verify you are trying with correct ip address or url.
change EC2 setting to Allow all IP address
and restart instance and try again

Laravel 5.2 swiftmailer error

I keep getting this error, despite trying all I could in the .env file. I even hardcoded the values in the config/mail file (removed them from the .env file), and it still gave the same error. I'm using a sandbox domain, with verified email addresses. The sandbox is active, and so are the email addresses.
PHP warning: stream_socket_client(): unable to connect to tcp://smtp.mailgun.org:587 (No connection could be made because the target machine actively refused it.
) in C:\xampp\htdocs\laravelproject\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Transport\StreamBuffer.php on line 267
Swift_TransportException with message 'Connection could not be established with host smtp.mailgun.org [No connection could be made because the target machine actively refused it.
#10061]'

Ispconfig 3: Error: Authentication failed. Error: Critical error Error: Could not connect to server

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.

Resources