Access Denied on store after removing wishlist

[vioray]

several times in the last few days I've tried to trim my wishlist but every time after removing one or two games I start getting

Access Denied
You don't have permission to access "http://store.steampowered.com/app/***/" on this server.

Reference #18.26aacd17.1511730060.16f368e3

or sometimes it's
Reference #18.9aacd17.1511730098.ed3c537
Reference #18.26aacd17.1511730127.16f5aa70

I'm then unable to use the store for approximately an hour before it just randomly starts working again

[smash]

Have you tried looking for solutions on Google? Seems to be a widespread issue with a few suggested fixes.

https://www.google.com/search?q=steam+permission+access+reference

For the most part, though, it looks like it's on Steam's side. And since the error produces a reference number, Valve must be aware of the problem.

[The Giving One]

Just did a quick forum search also, using basic terms. Got some hits. See if any of this may help also, in addition to what the good smash posted.

http://steamcommunity.com/discussions/forum/search/?gidforum=882959061466924237&include_deleted=1&q=%22You+don%27t+have+permission+to+access+on+this+server.

[vioray]

I have, but most suggest things like restarting steam (tried), disabling proxy/vpn (which I'm not using anyway), are advertising a game called "access denied" or just have a string of replies of "yeah me too" without any solution

[smash]

For sure, is this in browser (and which one, if so) or the Steam client?

[vioray]

happens in different browsers and in steam client

[smash]

Have you tried restarting your network router? That could be a quick 15 second fix (remember, though, there's always possible pain points when working with network stuff).

1. Leave VPN disabled
   
2. Shut down PC
   
3. Restart router
   
4. Start PC
   
5. Try editing your wishlist

[The Giving One]

Check your PC time and date, just in case.

http://steamcommunity.com/discussions/forum/1/135509124605142903/#c135509124605175921

EDIT..But it looks like the good smash is right, and it is on Valve's end. Everything I am seeing in the search results suggests the issue went away on it's own for many, after an update, or by simply waiting.

http://steamcommunity.com/discussions/forum/1/2217311444341550840/#c2217311444341580852

There, for example. If that exception number is the same or similar, perhaps.

[vioray]

tried restarting connection and computer, checked clock, still happens