For all of you experiencing this issue, maybe try resetting the machine and also deleting your cookies? Might help out.
Machine has been reset multiple times, including stopping and walking away for hours starting a new instance, as well as both Kali VM and host machine being shut down in between. Cookies are deleted every time browser closes.
Still encountering HTTP 500 Internal Server Error, which did not occur the first two times working on Spider. So, assuming something broken on HackTheBox’s end.
For all of you experiencing this issue, maybe try resetting the machine and also deleting your cookies? Might help out.
Machine has been reset multiple times, including stopping and walking away for hours starting a new instance, as well as both Kali VM and host machine being shut down in between. Cookies are deleted every time browser closes.
Still encountering HTTP 500 Internal Server Error, which did not occur the first two times working on Spider. So, assuming something broken on HackTheBox’s end.
Yep I had to switch from release arena to VIP to get it to work. Even then eventually i had an issue but i reset the machine, I wasted hours thinking the internal 500 error was supposed to be there. Silly me.
I was convinced I had something wrong last night, but now I think I was on the right track and it randomly quit working. It’s true if I go to the ‘classic’ interface I can spawn a VIP instance but I’d rather not share such an unstable machine with anyone else, either.
I did got the foothold. It’s not even that hard (could maybe be medium even, though I haven’t tried the privesc just yet) just rtfm and google around. It’s a little frustrating that it didn’t work right but if you’re having issues just reset it a few times or wait I guess, lol.
I solved the 500 by going to Login :: Hack The Box :: Penetration Testing Labs, the old site, and starting an instance from the “all machines” page instead of using the app vhost and launching it in release arena.
As for getting the foothold and user: figure out what you can control, figure out what your limitations are, establish something that works. One thing leads to the next, so don’t go off in a totally different direction if you get stuck. This machine really points you where you need to go, which is nice; I’ve enjoyed this one a lot.
if they had to throw 500 internal server error all over, what is the benefit of box being inside release arena. if i solve this box, am gonna give it the lowest score for sure.
maybe there was an issue on the backend sending the response object. it’s something totally unrelated to request cookie, and only manifesting in release arena. trust us guys we’re not crazy lol. maybe it was resolved by now or ephemeral, idk i already finished this box.
Rooted right now. Really a nice a machine!!
For 500 response errors, delete your cookies, if you have deleted them restart the machine.
User: don’t overthink it is all in front of you, be sure to look on all pages available. If you know how it is built you can control it. Don’t trust your eyes and trust what have you seen until now. Fight your limits, the backend technology provides you all the the bricks you need.
Root: it is not too different, think to what the server evaluate…
Oh dear…seems like an epic fail on enum for me. I only see a small number of endpoints and have tried the usual attacks on them but not getting anywhere. Gobuster turned up nothing that I couldn’t get with manual review - any nudge for what I’m missing?