https://add-on.ee.co.uk/status gives a 403 Forbidden error

[nancy_s]

Hi,

On both my mobile and for my dongle I get a 403 "Forbidden. You don't have permission to access this resource." error message when I try to access it.

I noticed this issue was reported in August and one of the suggested solutions was to clear the browser's cache, cookies etc. which I have done and it does not fix the problem.

Any suggestions? Thanks

[Jon_K]

Welcome to the community, @nancy_s.

Are you able to try using another browser?

Can you clear your cache and cookies again, then close the browser and try again?

Jon

[nancy_s]

Hi Jon,

I tried it on another browser and I get the same error even after clearing the cache, cookies etc. and restarting the browser. 

[Jon_K]

Thanks @nancy_s.

I'd recommend reporting this to our Customer Care team so they can check your account.

Jon

[nancy_s]

Will do. Thank you.

[prismprocess]

Hi Nancy,

I am sure the guy above is well intentioned he is talking complete rubbish. The probability of Customer Care knowing what is going on is somewhere between Nil and Zero percent as you already probably know. The first is it their fault not yours and they should accept responsible for their error.

A 403 Forbidden page is generated by a web server (their web server in this case) when it does not consider you to be allowed (meaning lack of permission) to view a resource. This is normally because what you are viewing it with has been disallowed. For example.... if you view the page with the latest versions of Microsoft Edge or Google Chrome you get a 403..... however if you view the same page with something old and rubbish like the browser in a not so smart tv it works (in other words....it is not your IP Address). I kid you not. It is a solution if you want to know your usage but is not ideal. It's quite funny that their web server would block their own customers like us...no? They should fix the page really by setting the correct permission (using CHMOD if its Apache) and/or for newer browsers (If it is browser sniffing) and/or removing any blocks that were created because of that.

So, to sum up....it is EE's fault not ours and they should fix it......pronto, without the usual deflection.

[grsdev]

I also noticed that you get the 403 when using Chrome. But when using Firefox it works fine (albeit giving me incorrect information, but that's another problem).

As you say, clearly not IP-related. Furthermore, I don't think it's related to the User-Agent: header either because I can change that at will and I still get a 403.

[nancy_s]

Thank you. Hopefully our friends at EE are reading these exchanges and will look into resolving this issue in particular since this is not an isolated incident related to one user. There were a number of reports before in the community and one specifically back in August.

[grsdev]

Update: even Firefox on the laptop (the browser that actually worked earlier) is now giving me a 403.

Tried so far, all unsuccessfully:
Chrome 107 on Windows 11 laptop
Firefox 106 on Windows 11 laptop
Latest versions of Chrome, Firefox and Samsung Internet on an S22 Ultra running Android 13

This could be linked to the outage that's causing zero allowance to be reported to all PAYG users at the moment.

[Jackyg]

Thanks for your insight here. I've been unable to add data for a week now but it's good to know it's an EE problem not mine.  Has anybody been able to resolve it by going to their care team or any other suggestions?