cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This page is no longer active

close

   

For up-to-date information and comments, search the EE Community or start a new topic.

AWS Server Connection with EE 4G Network

hash1
Contributor
Contributor

I am doing work from home by using 4G data. For the last few days, I am not able to access my AWS servers because of IPv6 implementation of your network. Whenever I search what is my IP, it is showing me IPv6 address, due to some problem at your end, I am not able to access my server because my server access is not fully opened, I have to add my IPv4/IPv6 IP into security group with a port number when I select my IP in security group selection, I am receiving this IPv4 address 213.205.240.207/32 but its not working, please solve this problem, I am not able to connect with IPv6 address as well to AWS servers. I tested it by opening all traffic to my server which means 0.0.0.0/0 it is able to access but when I put my live IPv4 or even IPv6, it's not working, this happens sometimes and stay for a very long time and solved automatically, it means there is a problem at your end. Please solve this problem. I am not able to do my work.

5 REPLIES 5
Jon_K
Former EE Employee

Hi @hash1.

 

Welcome to the community.

 

I'd recommend getting in touch with our Tech Gurus about this so they can look to raise an investigation ticket.

 

They will be able to help you further.

 

Jon

Please reply this, there is a problem running in EE. I am not able to connect my servers using IP. However, I can connect using a domain name. But some tools like DBeaver are not able to connect with server either with domain name. @Jon_K 

Christopher_G
EE Community Support Team

Have you spoken to our Technical Support team, @hash1?

 

As @Jon_K suggested, they may be able to help you with this.

 

Chris

Do you think they can help me? I tried to call them but all in vain. @Christopher_G 

Christopher_G
EE Community Support Team

If anyone from our side can, it would be them, @hash1


Chris