Sorry: The website is offline?

On both chrome and Microsoft edge, I get this error from my computer. It doesn't happen with any other website. I tried clearing cookies (since it might be registering the data in a weird way) and it does not solve the problem. I have to use internet explorer to connect to the website. Anyone know what might be the problem?

You might also try clearing your cache. Sometimes funny things get cached.

For what it's worth, Firefox isn't giving that error.

Nope. That doesn't work either.

I'm using Chrome right now and having no trouble with the website.

Sorry, the website is currently offline.
Sorry, the website is currently offline.
[ { "src": "CMS", "msg": { "status": 200, "statusText": "OK" }, "timestamp": 1598224799712 }, { "src": "CMS", "msg": { "status": 200, "statusText": "OK" }, "timestamp": 1598224799741 }, { "src": "API/accounts/getHeader", "msg": { "status": 200, "statusText": "OK" }, "timestamp": 1598224800148 }, { "src": "api/store/getCart", "msg": { "status": 403, "statusText": "Apple" }, "timestamp": 1598224800309 } ]

Maybe this might help.

Sorry, but is at your end.
Chrome, Edge, Firefox all work for me.

Papa - But why would it only not work for the paizo website? Why is that website literally the only website I can't access?

HTTP response code 403 is access denied. Are you able to see the store if you're logged out?

I can log into the store from Explorer.

I can't even "log out" of my acct if I cant get to the page.

I can't even "log out" of my acct if I cant get to the page.

But... you're posting here on the forum. So you can get to (part of) the web site. Up in the menu is My Account, and the bottom of that has Sign Out.

The possibilities here are:
1} It's something with your PC.
2} It's something with your account.
3} It's something with a specific Paizo server.

Odds of #3 aren't terribly high as long as there's only one person (you) reporting this. It's not impossible, but not likely.

#2 should be relatively easy to test, which is why I'm suggesting logging out. That and 403 is 403.

#1 I don't know what it might be. Chrome and Credge (assuming you've got the modern Edge) are effectively identical, so it's not shocking that something that impacts one impacts both.

Um, yeah, I just realized that you're probably posting using IE, and failing with the other browsers. Duhr. Sorry.

Maybe try an InCognito/InPrivate window?

The possibilities here are:
1} It's something with your PC.
2} It's something with your account.
3} It's something with a specific Paizo server.

Or a DNS server has a corrupt address array. (again, not likely if Paizo can be reached using one browser but not another on the same computer.)

Verzen, if you haven't already done so, log out of your Paizo account, open your Chrome browser, clear your cache, clear your Paizo cookies, close it.

Open your Edge browser, clear your cache, clear your Paizo cookies, close the browser.

Shut down your computer.

After you reboot, try Chrome first, then Edge, and see if you've solved the problem

Verzen wrote:

I can't even "log out" of my acct if I cant get to the page.

But... you're posting here on the forum. So you can get to (part of) the web site. Up in the menu is My Account, and the bottom of that has Sign Out.

The possibilities here are:
1} It's something with your PC.
2} It's something with your account.
3} It's something with a specific Paizo server.

Odds of #3 aren't terribly high as long as there's only one person (you) reporting this. It's not impossible, but not likely.

#2 should be relatively easy to test, which is why I'm suggesting logging out. That and 403 is 403.

#1 I don't know what it might be. Chrome and Credge (assuming you've got the modern Edge) are effectively identical, so it's not shocking that something that impacts one impacts both.

"But... you're posting here on the forum"

From internet explorer. Different web browser. This only happens in Chrome and Edge.

Well, Chrome works now but Edge still doesn't....

I was having this issue on Chrome for about a week. Worked in IE with no problem (never tested Edge). Clearing the cache in Chrome settings resolved the issue for me as well.

Definitely recommend giving that a shot in the Chrome settings page:
chrome://settings/clearBrowserData