Did you reset the data?i typed the https;// and then my ip, it just loads for a long time and then say could no display page
Go to your computer IP adress with the Wii U browserI execute startServer.bat.... but host it in 0.0.0.0:80... that isnt my ip (obvious) and i writte it on my Wii U and dont work. What im doing bad?
i typed the https;// and then my ip, it just loads for a long time and then say could no display page
I execute startServer.bat.... but host it in 0.0.0.0:80... that isnt my ip (obvious) and i writte it on my Wii U and dont work. What im doing bad?
yeah, https is for secure websites. look at the url for temp, the green lock means it's secure. it uses https.
i used a colon and http and it just says could not display imageit uses a colon, not a semi colon. the reason the lock doesn't always appear is that something on the thread/post isn't secure. it could be something as innocuous as an image which it usually is. I have a tutorial on self-hosting. I'm not sure if it's any different on 5.5.2 though since I'm still on 5.5.1. u can easily self-host with xampp. that's what I'm using for both the wii u and ps4 exploits. I was using mongoose, but I wrote a note on using xampp which is very simple. a tutorial isn't even really needed due to ease.
i used a colon and http and it just says could not display image
i followed your steps exactly so i have no ideafollow these steps EXACTLY and it will work:
https://gbatemp.net/threads/haxchi-on-5-5-2-self-hosting-method.481209/
i followed your steps exactly so i have no idea
Yes I see itdo you see the web page on your PC or Mac when you launch mongoose?
Yes I see it
it just loads for a while and then says error code 112-1028 could not display imageok.. now what happens when you go to your Wii U web browser (reset the save data, open the curtains) and type in the FULL address as shown in your browser address bar i.e. :
http://192.168.1.50:8080
it just loads for a while and then says error code 112-1028 could not display image
i assume there is something you're missing from pangsters steps that you dont know about, did you reset browser data and make sure that your curtains were open and also that you had DNS set to auto obtain while trying to access the exploit page? Are you using mongoose?it just loads for a while and then says error code 112-1028 could not display image
Yes to alli assume there is something you're missing from pangsters steps that you dont know about, did you reset browser data and make sure that your curtains were open and also that you had DNS set to auto obtain while trying to access the exploit page? Are you using mongoose?
I've tried all of these and nothing seems to workhave you set your DNS to AUTO ASSIGN?
--------------------- MERGED ---------------------------
have you also made sure that your WIi U and PC/Mac are on the SAME network?? - if you cna see the screen on your Pc then there isn't an issue with hosting it or serving it to your local network.. the issue is with your Wii U connecting to it!
this tells me that one of the following is the issue:
- you've not cleared/reset the browser data and not opened the curtains on the Wii U browser AND clear your COOKIES!!
- you're not on the same network as your PC/Mac (can happen for example if you split the WiFi connection between 2.4 and 5 GHz)
- You've not set the DNS to auto obtain (or used Google settings etc) so it's not being routed to the correct address
- You have problems with how your router is setup ( as a temp by pass you could always place the Wii U in the DMZ) or follow the instructions here as it seems to have been an issue in the past for some users: http://www.ign.com/boards/threads/wii-u-browser-problem-im-the-only-one.452788554/
to be clear - this is not an issue with the exploit or instructions provided.. there is clearly something SPECIFIC to YOUR setup that is preventing your Wii U connecting to the webpage thats being served! - you'll need to sort it out - either by following the above or doing some googling! - do you have Skype installed or running or any anti-virus?.. try disabling these for 10 minutes or so or changing the port from 8080 to something else and see how you get on....