Select Open as Desktop and it should open in a new tab in your web browser. I know you’re probably trying to be cautious but always try to experiment. That to me is the fun part of pentesting.
I was struggling with this same error. I played around with the browser some and turned off enhanced tracking protection (the little shield in the url bar) and then got the {“status”: “running”} like it’s supposed to. Hope this helps someone.
1 Like
yeah i’m having the same issues no matter what. I tried to do it via the pwnbox but i don’t think aws tools are installed
Looks like it is normal behavior. Probably script deploys S3 instance. And it took some time. S3 is available after ~15 min
1 Like
What solved it for me was:
- Resetting the machine once.
- Only entering s3.thetoppers.htb into /etc/hosts without thetoppers.htb
Hey everyone! I think I found a solution. I hope the thread is helpful to someone else in the future.
The first I suggest is regenerating the vpn, soft-reseting the virtual machine and checking the /etc/hosts. I’ll remind you that the s3 subdomain and the toppers.htb domain url should be on the same line in this way:
<ip> thetoppers.htb s3.thetoppers.htb
If any of those options doesn’t fix the problem, the solution I found useful is to clear your browser cache and flush your dns cache. If you’re using a debian distro (I’m using kali) the following command may do the trick:
$ sudo resolvectl flush-caches
Hope someone finds it useful, happy hunting 
I was just experiencing the same Proxy Error. However, it seems that the proxy server is initiated and is enable on request. I ran the request through curl about 3 times consecutively… and about a minute later, the page was loaded as expected.
Hopefully this helps
Hi, once again, 502 proxy error, solve with only entering s3.thetoppers.htp in hosts file. no need reseting
1 Like
Still having the same issue
Hi all. The fix for me:
Just be very very very patient. I waited about 10 mins or more and it worked. You can just curl the page to test. I had the proxy error then it just started to work. My hosts file looks like this too.
<ip_address> s3.thetoppers.htb thetoppers.htb
1 Like
“s3 proxy error?”
you should wait for 15 min for the bucket to go online (don’t try to be clever, don’t write anything in /etc/host/ except the thetoppers.htb you found) then used gobuster to enumerate it.
“gobuster don’t show me the s3 what is happening? is it because my ip? should i use vpn?”
NO, ( read the walkthrough carefully!! ) check your gobuster version with “gobuster -version” gobuster 3.2 above (assume yours is 3.4) should use “–append-domain” flag to append the wordlist so the gobuster would do this “[wordlist].theroppers.htb” instead or it wouldn’t find any s3 domain because the tool won’t append it!
after you find the subdomain, try to access it, if it still gives you the proxy error, you should input the s3 domain to your /etc/host/ then grab the banner with curl or whatever, it would shows [“status”:“running”] hope this help NOOBS, you learn something today that actually always happen in real life by professional which is reading problem the biggest enemy of hackers, avoid cleverness it makes things more complex and harder, try to be careful next time and good luck, enjoy studying!
The challenge sucks, sometimes the bucket is randomly up, sometimes it won’t go up even after an hour…
The error message “Proxy Error” typically occurs when there is an issue with the proxy server that is being used to access a website or other online resource. This error message may indicate that the proxy server is experiencing technical difficulties or that there is an issue with the network connection between the client device and the proxy server.
If you are experiencing a Proxy Error while trying to access a website, there are a few things you can try to resolve the issue:
Refresh the page: Sometimes, the error message may appear due to a temporary issue with the connection. Try refreshing the page to see if this resolves the issue.
Clear your browser cache: If the issue persists, try clearing your browser cache and cookies. This can help to remove any corrupted data that may be causing the issue.
Disable proxy settings: If you are using a proxy server, try disabling the proxy settings and accessing the website directly. This can help to isolate the issue and determine whether the problem is with the proxy server or the website itself.
Regards,
Rachel Gomez
I am experiencing the same thing. I tried all the different solutions above and waited hours to see if it would kick back on. Even rebooted the box many times and I’m still getting the same issue. I am 99% done with tier one and only need to submit this machines flag and I cannot move on to tier 2 without finishing this machine. This is very frustrating 
.
Yes. Thanks)
Did this today and had the same issues at first, but after a few minutes it worked.
What i did:
Added “10.129.50.83 thetoppers.htb s3.thetoppers.htb” to the hosts file, then I got the proxy error.
Waited for ~5-10 minutes, then the website displayed “{“status”: “running”}”.
For anyone else who’s dealing with this, it’s very easy to know if your hosts file is at fault here. Simply ping s3.thetoppers.htb the ping response should look like PING thetoppers.htb (YOUR_SERVER_IP_HERE). If the IP is there, then your name resolution is working, so it’s not your hosts file. For me, my name resolution is working fine and yet, I still get the proxy error. I’ll try again later I suppose
EDIT: Yep, just stopped my box instance. Then waited a bit and spawned a new one and it works! pwned
Hey,
The problem with proxy error is solved this video. This explains why you get this error and how to fix it.
Cheers,
Guys, i had this error after restart the challenge, i couldn’t get the cmd results in the browser, so i restart everything (vpn, machine, vm…) and i had Bad Gateway running the aws command.
You should clean the browser cache, i also removed the dns resolution in etc/hosts and added it again (idk if it helps).
So that’s how i solved it, i hope this would be useful.
peace
For people who may have this problem in the future: just wait and let the machine run for few minutes (10-15 min).