1 Answer
- Newest
- Most votes
- Most comments
0
I faced a similar issue a few months ago, and I was able to resolve it by rebooting the instance. I recommend trying this solution to see if it resolves the error. Please reboot the instance and let me know if the issue is resolved. Thank you!
answered a year ago
Relevant content
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
I did that, but the issue never resolved and it happened on different instances as well when in the initial one this issue happened I terminated that instance and relaunched a fresh one it again happend on this fresh one and I rebooted it multiple times upon rebooting the instance multiple times also the issue was not resolved
Since I was only testing Apache2 Squid and Nginx and configurations I did it on a open ubuntu virtual box
If I will face this issue again and if your solution works I will let you know
Thank you Best Regards