OPR Error 403, is there a workaround?
Cosk62
✭✭
I occasionally get error 403 when trying to view a full-size image of portal nomination. This happens only with nominations coming from Ingress Prime (never from Redacted). When this error happens it affects both the portal photo and the supporting photo.
Here is today's example.
Portal photo - lh3.googleusercontent.com/ubNm47ZkWQqMt4jM2QlgpRgMAl7gUeydg9-Q2ATrH-kOnCz7gpVf_nBnbnakXDJ5LaMkstEvsa7tQ6bmNzQklwrWkLSC=s0
Supporting photo - lh3.googleusercontent.com/WH5wctXghw7mukvA6qKjckUzlqnOudNxIbhEcdy5GpzpaZM4ly85DdsTkQccimtbTk-f6AIUBw1J8z6DaLXwXyZq7Q=s0
Anybody knows of a workaround?
If somebody at Niantic is seeing this, nomination coordinates are 42.577919,-72.331817. Hopefully coords are enough to identify the problematic nomination.
Tagged:
0
Comments
This works sometimes, the end of the full url, you'll see =s0, change that to either =s1000 or =s1600
Thank you @LemoMcLemonFace , that'll help for a transitional period. But this shouldn't be a permanent solution for Niantic.
@LemoMcLemonFace Thanks a lot! Works.
@DerNarf no need to worry about it being permanent, Niantic themselves said this is a work around that is only necessary for the first couple of days with prime subs.
Apparently there was a permissions error when the pics were uploaded and so causing the error when you try to view them in full detail in OPR.
Its since been fixed so anytime you get the error it is only from a sub from the first couple of days of prime submissions.
Thanks @LemoMcLemonFace !
I wonder if that's the same reason why the photos don't get saved to the device?