LaravelCollective/remote has been working great for quite some time. I needed to change the IP address of one of the servers, so off to app/remote.php I went. I made the change. In my Laravel project, I can php artisan tinker and SSH::into('dhcp_server')->run(["ls -l /etc"])
However, one of my Listeners calls SSH::into('dhcp_server').... also. When I fire the event, the listener executes, but is trying to use the OLD IP that is no longer in app/remote.php. I am very confused as to what might be causing this. Artisan commands I've blindly run: clear-compiled, cache:clear, config:clear, config:cache, and view:clear. Still it continues to attempt to connect to the old IP. Here is the error. The IP shown here is the old IP.
production.ERROR: ErrorException: Cannot connect to 10.0.0.101:22. Error 113. No route to host in /usr/share/nginx/html/goldaccess/vendor/phpseclib/phpseclib/phpseclib/Net/SSH2.php:1011
Hello,
LaravelCollective/remote has been working great for quite some time. I needed to change the IP address of one of the servers, so off to
app/remote.php
I went. I made the change. In my Laravel project, I canphp artisan tinker
andSSH::into('dhcp_server')->run(["ls -l /etc"])
However, one of my Listeners calls
SSH::into('dhcp_server')....
also. When I fire the event, the listener executes, but is trying to use the OLD IP that is no longer inapp/remote.php
. I am very confused as to what might be causing this. Artisan commands I've blindly run:clear-compiled
,cache:clear
,config:clear
,config:cache
, andview:clear
. Still it continues to attempt to connect to the old IP. Here is the error. The IP shown here is the old IP.Thoughts?