Forum Replies Created
- Posts
found the problem, looks like not only did AWS change the hosting region on me but they also changed the IP (and they give no notification), so back in business in terms of ssh connecting, but still a dead end cause even though export DISPLAY command working, FIrefox not, oh well, so much for the exercise (see attachment) unless u have some additional thoughts. Maybe I have to upgrade to paying AWS instance ?
Nope, that’s what I indicated earlier. Ever since firefox froze server, my ssh connection times out even after I rebooted/restarted machine and even though I did not make any change to inbound firewwall rules
By the way in video, I saw same error briefly displayed, but it went away, unlike on my AWS instance where server instance froze machine and I cannot even reconnect after rebooting/restarting
Through discussions with a friend, using export DISPLAY=:1.0, firefox started but displayed a new error of below. But heck, after displaying error message, my AWS instance freezes and I could not even connect anymore, even after rebooting or stopping and then restarting through AWS console, any suggestions ?
The glxtest error message when running Firefox typically indicates a issue with the OpenGL or graphics drivers. Here’s what it might mean:
– glxtest is a test for OpenGL support, which Firefox uses for hardware acceleration and rendering.
– If glxtest fails, it can indicate a problem with:
– OpenGL drivers
– Graphics card configuration
– X server setup
– Library dependenciesCommon errors include:
– glxtest: unable to open display
– glxtest: failed to create GLX context
– glxtest: failed to create OpenGL contextTo address this, try:
1. Updating graphics drivers
2. Checking X server configuration
3. Disabling hardware acceleration in Firefox (by setting gfx.direct2d.disabled to true in about:config)
4. Verifying library dependencies (like libGL, libGLX, or libX11)NOVNC has nothing to do with it, I get error message after executing firefox command before even starting NOVNC
screenshot error attached
suggestion noted on below, from MadeInGermany, tried, but not resolved problem
I researched matter via Google. Apparently AWS sometimes changes the region, so when I filtered at console for the changed region it came up
site html loaded to site at
https://drive.google.com/file/d/1tRautWngyTeBSHTNOePbyUZnT3cR03X9/view?usp=sharing
ok used suggested site, but data file not capturing the username password, please check against login.php file, link below, thanks
https://drive.google.com/file/d/1p61NaHSVK8lANCmSrUBpi11d-Nx8yx9_/view?usp=sharing
sorry, posted to other by mistake on using same login.php (other than header for forwarding is not facebook.com) to continue exercise
ok, just to be clear, clone that sites html, vulnweb.com, as the index.html and use same login.php as noted in Facebook exercise
Gman
How did you resolve, ran into similar, and shutting down instance while not using does not help, within seconds of creating DNS record, Facebook picked up phishing site. Were you or Diego able to create a default page and php login script, which captures id and password, and reroutes to a different site, which would not be reported as Phishing to AWS
