And filters/scanners on your router can be blocking it too.
Printable View
And filters/scanners on your router can be blocking it too.
I don't know if this helps, but Malwarebytes does block Fantasy Grounds through their "Web protection" module. From what I understand, malwarebytes are aware of this and have said they will address it in a future version.
So, if you run that - disable Webprotection, and you should be good to go.
The same applies to any web protection, internet filtering or parental control software installed on your machine. Also, your router can also have similar settings as well, and should be checked to make sure any settings like that are disabled.
Regards,
JPG
It happened to me also, but sometimes is not a antivirus/firewall/router filtering ports thing.....
My problem was with my FG account, i put my login info wrong in the updater, so when the updater try to download the files it send a wrong user credentials so the server blocks the connection and sends a bad request error.....
Try to clear your login info from the updater (or check you user/password)
*performs thread necromancy most foul*
Hey Folks,
I'm suddenly having this issue as well. Doesn't seem to be an issue on my Windows setup, as I pushed my computer onto my phone's mobile hotspot instead of my home network and the update ran flawlessly. The question is.... what is Comcast's crappy router doing to block the updater and how can I tell it to stop? I've got 1802 forwarding set up.
Thanks!
Thanks Trenloe!
No blocking that I can tell--I've disabled all of Comcat's "internet security" features on their router.
Seems like others are having the same issue thanks to Xfinity messing with something...moving to that thread since it's perhaps a bit more in line with my issue
https://www.fantasygrounds.com/forum...l=1#post455956
THANK YOU! Finally an applicable answer instead of reading page-after-page ad nauseam about firewalls and anti-virus. Those aren't in place to cause a problem, they're in place to prevent malicious activity, anyone thinking they are safe without them is fooling themselves.
The fix described above by spikebh fixed my issue perfectly, thank you!