The Envoyer Documentation lists the following 2 IP address's to Whitelist on your firewall.
45.56.118.59
45.56.113.44
Even after I added these IP Address's to my EC2 Security Group for Access via Port 22 Envoyer was not able to connect to my service. Once I disabled Port 22 firewall completely Envoyer was able to connect just fine.
Not sure if this is just an Amazon thing and I am setting up the Security Groups Wrong (I doubt it I have about 2 dozen rules that all work perfectly including my old SSH rules for my old Deployment service) or there are new (or more) IP Address's for Envoyer.
I've been using Envoyer since launch with those 2 IP addresses on AWS without any issues, it stops working if I remove the security group so it's definitely correct.
Thanks @danwall . I obviously am doing something wrong. I've been using EC2 for 7 years and never run into this issue. I just need to sit down and take some time to work through the problem. But good to know it's user error, because I have more control over that than anything else :)
I don't know that it is user error. I'm not hosting on AWS but with a fully managed hosting provider. I had the provider add both IPs to the firewall (not something I have access to, so I know it's setup correctly). Envoyer still can't connect. I suspect maybe there are more than just the 2 IPs now and that list needs to be updated.
I take it back, it was user error. My hosting provider messed up the firewall rule. Also, I emailed Envoyer support and Taylor confirmed those are the only IPs for Envoyer.
Diddo for me. I had emailed Taylor after I originally posted and he confirmed. Next week I'll sit down and hammer out my own issue and if it's something I think others might run into I'll update the thread.