Open RodrigoDornelles opened 3 years ago
The game DOES start up for me:
Now I've been discussing this with others who have similar issues, and at this moment there appear to be two likely scenarios that appear both not the be of Game Jolt's doing. Either it's the ISP having issues (one person could get around this by using an open wifi spot) (that person normally uses xfinity), or this could be an aggressive virus scanner blocking the page off due to scripts it doesn't know (Avast was named as a possible source of evil, and knowing Avast, I deem it likely possible).
Also that picture on the background seems really odd, and really looks like a 3rd party is blocking things off.
Same! It has the same message and the same photo of a guy with a notebook/binder which he is holding with his arm. I tried to play my own games and other peoples but it will not work. Game Jolt Team, please fix this soon.
This is a very interesting post on the forums, it seems to fix the problem for all who suffer:
This is a very interesting post on the forums, it seems to fix the problem for all who suffer:
I am sure I will have to pull up the menu as done in the image above but how do I get there? Note that I am using Google Chrome, and the 2 Ad-Blocker extensions called Bitdefender and U-Block Origin and I am using Windows 10 as used in the image above. I also searched in the search bar WLAN and WLAN Properties but the setting thing did not show up in the search results.
This is a setting in Windows itself, I think and not inside any browser. Since I never had this issue myself I never messed with that stuff...
I'm getting the same 403 error w/ the notebook guy. Also looking for that WLAN window if u figure out how to find it lmk plz thx !
this problem cannot be ignored by the gamejolt team, as a solution on the user side is terrible for users to know how to solve.
The question is if the Game Jolt team is the party to blame. When it's not, then the team can only ignore it and then the responsible party should come up with a fix. If the solution lies only on the user side to solve, terrible as it is, you can still not expect GJ to hack their user's computers... Things are a bit vague here to point fingers....
Oh, btw this is a duplicate of #1444 -- Just noticed.
The question is if the Game Jolt team is the party to blame. When it's not, then the team can only ignore it and then the responsible party should come up with a fix. If the solution lies only on the user side to solve, terrible as it is, you can still not expect GJ to hack their user's computers... Things are a bit vague here to point fingers....
I would still expect a reallocation, such as reworking the availability of games for a provider other than this problem.
They have just move to a new dns, however sometimes clients can linger on the old data for a very long time. A few games of mine don't accept the GJ API any more... For one game I could "fix" it by merely switching to http in stead of https. I have a feeling this issue could be connected to that move and not all programs this picking up the way it should... Makes me still wonder why the site itself works and the games do not, but then again, when I see how where the pictures uploaded to GJ are stored, which is on a domain that is completely different, so I guess webgames are also on a different domain and could therefore be troublesome. And if there's then a data conflict due to moving from old to new and old data lingering, some security protocols can block stuff out. Since some people fixed the issue by using a different provider, this could be the case, as using a different provider quite often forces all involved computers to have their data flushed or at least to use new data for the new provider.
The question is if the Game Jolt team is the party to blame. When it's not, then the team can only ignore it and then the responsible party should come up with a fix. If the solution lies only on the user side to solve, terrible as it is, you can still not expect GJ to hack their user's computers... Things are a bit vague here to point fingers....
The issue is almost definitely on the server side of things at the very least. (Possibly, with their CDN provider - DataCamp's CDN77) This is not something over which the user has control. Disabling IPv6 on the client is a workaround, not the fix.
Flushing the DNS cache - not that it matters, the TTL for these records is incredibly short: the reproduction steps I noted here a while ago: https://github.com/gamejolt/issue-tracker/issues/1444#issuecomment-748410000 still produce the same result.
How are you using Game Jolt? by the brave browser.
Please describe the issue you are having my game is giving 403 error when trying to play in browser.