Can not run successfully after reboot my server

[123ysys]

Before reporting a bug, please see our FAQ in FAQ.md!

Description

Can not connect to the proxy setup on AWS EC2 on my whatsapp client. And some errors happen on EC2 console.

Failed Step

1. Open all the ports mentioned on this script "docker run -it -p 80:80 -p 443:443 -p 5222:5222 -p 8080:8080 -p 8443:8443 -p 8222:8222 -p 8199:8199 -p 587:587 -p 7777:7777 whatsapp_proxy:1.0" on AWS Safety Group
2. run the all the command from "git clone https://github.com/WhatsApp/proxy.git" to "docker run -it -p 80:80 -p 443:443 -p 5222:5222 -p 8080:8080 -p 8443:8443 -p 8222:8222 -p 8199:8199 -p 587:587 -p 7777:7777 whatsapp_proxy:1.0
   "
3. Received these messages:

[PROXYHOST] No public IP address was supplied as an environment variable.
curl: (22) The requested URL returned error: 401
[PROXYHOST] Failed to retrieve public ip address from AWS URI within 2s
[PROXYHOST] Public IP address (3.18.201.251) in-place replacement occurring on /usr/local/etc/haproxy/haproxy.cfg
/home/haproxy/certs /
----------------------------
| SSL Certificate Generation |
----------------------------

--> Certificate Authority
Generating certs for TSWbQoo02TO2h9Mw.net
====> Generating new CA key ca-key.pem
====> Generating new CA Certificate ca.pem
-----BEGIN CERTIFICATE-----
*******
-----END CERTIFICATE-----
====> Generating new config file openssl.cnf
====> Generating new SSL KEY key.pem
====> Generating new SSL CSR key.csr
====> Generating new SSL CERT cert.pem
Certificate request self-signature ok
subject=CN = TSWbQoo02TO2h9Mw.net
====> Generating SSL CERT / KEY COMBO proxy.whatsapp.net.pem
Certificate generation completed.
/
/
[WARNING]  (28) : Server wa/g_whatsapp_net_5222 is DOWN, reason: Layer4 timeout, check duration: 60003ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
[ALERT]    (28) : backend 'wa' has no server available!

after running the

RUN

command.

More Details

Run "docker run -it -p 80:80 -p 443:443 -p 5222:5222 -p 8080:8080 -p 8443:8443 -p 8222:8222 -p 8199:8199 -p 587:587 -p 7777:7777 whatsapp_proxy:1.0",
Output "

[PROXYHOST] No public IP address was supplied as an environment variable.
curl: (22) The requested URL returned error: 401
[PROXYHOST] Failed to retrieve public ip address from AWS URI within 2s
[PROXYHOST] Public IP address (3.18.201.251) in-place replacement occurring on /usr/local/etc/haproxy/haproxy.cfg
/home/haproxy/certs /
----------------------------
| SSL Certificate Generation |
----------------------------

--> Certificate Authority
Generating certs for TSWbQoo02TO2h9Mw.net
====> Generating new CA key ca-key.pem
====> Generating new CA Certificate ca.pem
-----BEGIN CERTIFICATE-----
*******
-----END CERTIFICATE-----
====> Generating new config file openssl.cnf
====> Generating new SSL KEY key.pem
====> Generating new SSL CSR key.csr
====> Generating new SSL CERT cert.pem
Certificate request self-signature ok
subject=CN = TSWbQoo02TO2h9Mw.net
====> Generating SSL CERT / KEY COMBO proxy.whatsapp.net.pem
Certificate generation completed.
/
/
[WARNING]  (28) : Server wa/g_whatsapp_net_5222 is DOWN, reason: Layer4 timeout, check duration: 60003ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
[ALERT]    (28) : backend 'wa' has no server available!

". -->

<Linux/Unix Platform -->

[eozturk1]

Please check your configuration settings to ensure the backend at g.whatsapp.net:5222 is accessible from your EC2 instance. This might be related to AWS configuration settings.