Awoo-Installer
Awoo-Installer copied to clipboard
Huntereb
Keep having trouble with HTTP header... failed request
keep trying to connect but get but get this in the fail window:
PerformRequest93: Failed to retrieve HTTP header. could not connect to server.
My pc is wired to router, switch is on wifi... any ideas? The usb install when connected to pc is great! but wireless is a problem.
keep trying to connect but get but get this in the fail window:
PerformRequest93: Failed to retrieve HTTP header. could not connect to server.
My pc is wired to router, switch is on wifi... any ideas? The usb install when connected to pc is great! but wireless is a problem.
I have your same problem but I've find a solution with a mac. My Mac is connected to the router via wifi , if you are able to connected the pc via wifi you should be able to install the games via network with awoo installer. In alternative, if you use a VM with windows, follow this steps. So this method worked for me cause i'm using a mac with a windows 10 x64 on virtual machine via VMware fusion. So if this is your same condition this method can worked for you too. This problem is related to the ip address connection on mac, so if you use windows on VM, go to VM settings > network adapter > change the selected box from "share with my mac" to the box "wifi". So now the windows VM create a dedicated connection with no issue. Now the installation via Network with Awoo Installer should work out. Hope this solution can worked for you and the developer.
Same here with win10 64bits. After selecting to install on the SD card, it changes to installing but after a few moments gives this error.
Same here using NS-USBload v2.2. It sends the lists the list of nsps fine, but fails trying to install them. I've disabled the firewall on Windows and my router to no avail.
Yeah i've got this issue too and it needs to be solved. I was really looking fordward to installing my games because for some reason my switch isn't detected on my computer and because of that i can't do wirless either. this issue needs to be fixed please. I'm using ns-usbloader and a windows computer. Maybe i should try and connect my pc to ethernet.
This is likely a firewall issue pc-side. Try disabling Windows firewall, or whatever Mac OS uses for a firewall.
Ok I will try that Huntereb, thank you for your help. I will reach out to you again if it still doesn't work.
From: Huntereb [email protected] Sent: Monday, May 4, 2020 4:01 AM To: Huntereb/Awoo-Installer [email protected] Cc: Ali-Asim800 [email protected]; Comment [email protected] Subject: Re: [Huntereb/Awoo-Installer] Keep having trouble with HTTP header... failed request (#47)
This is likely a firewall issue pc-side. Try disabling Windows firewall, or whatever Mac OS uses for a firewall.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Huntereb/Awoo-Installer/issues/47#issuecomment-623236016, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APLCO6LYZ34GW4UVCIPH72DRPYVYHANCNFSM4LB4WSXQ.
This is likely a firewall issue pc-side. Try disabling Windows firewall, or whatever Mac OS uses for a firewall.
Yeap, same problem on MAC and disable my antivirus did the job.
Not sure if this is related, but I've been having an issue installing from both Google Drive and URLs. It shouldn't matter that I'm on MacOS because the switch shouldn't even be connecting to it. I'm sure the files are publicly accessible. I get the following error:
HTTPDownload:157: Failed to retrieve HTTP Header: SSL connect error.
I've tried going into the code to see if I can get more info on this with easy_curl's errorbuffers, but no luck.
Not sure if this is related, but I've been having an issue installing from both Google Drive and URLs. It shouldn't matter that I'm on MacOS because the switch shouldn't even be connecting to it. I'm sure the files are publicly accessible. I get the following error:
HTTPDownload:157: Failed to retrieve HTTP Header: SSL connect error.
I've tried going into the code to see if I can get more info on this with easy_curl's errorbuffers, but no luck.
same here, did you find any solution? i believe the first two versions worked. is it possible to rollback or will sig patches not allow it?
@JoshuaManuel @donjonne this is because you're using a Switch with its prodinfo wiped. This will be fixed on the next release. (You will have to manually update)
@JoshuaManuel @donjonne this is because you're using a Switch with its prodinfo wiped. This will be fixed on the next release. (You will have to manually update)
@Huntereb i actually got it running a while back ago never been on prodinfo hide mode(dont trust people with my certs) sorry for not giving updates here is something i found:
- for gdrive id- for some reason my computer pc gives me the letter "I" (big i) the same as "l" (small L) so finding this out it fetched the correct link
- i believe i was not connected to the internet one time(what else could it have been idk) -is there a way to incorporate the wifi signal in the app as to probe that user is indeed with internet connection?
- quota for original g drive link was exceeded -just made a copy to my personal drive and made a public link
i believe the last problem is the most common one tbh
@donjonne You can't access the net install page if you don't have access to a wifi connection. You may have disconnected while entering the ID or something. Just try again next time. :P
@donjonne You can't access the net install page if you don't have access to a wifi connection. You may have disconnected while entering the ID or something. Just try again next time. :P
yea very odd anyways all is working good since last game i installed was a xcz thru a public gdrive link for the game: "awesome italian 3d guy" lol
for me the problem in the end was that windows was blocking ns-usbloader. had to cancel the blockage in properties
I had the same issue on my m1 mac os and my problem was due to the VPN being turned on. I turned off the active VPN and it worked fine.
Hello,
I solved it with enebale Java communication in public network in Windows Defender Firewall.
Anyone else coming across this in 2023, I was able to fix this by disabling "Windows Defender Firewall" on my private network.
