Jamf Push Proxy returned status of: 403

lashomb
Contributor II

Curious if any environments are still seeing these types of errors running 10.8?

3 REPLIES 3

ThijsX
Valued Contributor

@lashomb Hi,

I have not seen the 403 for a while, current build : 10.8.0-t1539715549
When the 403 appeared, i deleted the Push Proxy Certificate and recreated.

gsabari
New Contributor III

Yes we are seeing these warning in our environment. It is occupying our logs completely

remyb
Contributor

Try to contact JAMF support, the issue causing these is supposed to be fixed, but 'old' notifications are probably still in the queue, causing these errors. Or you could go through the steps below, which JAMF support gave me.

BE AWARE! DO THIS AT YOUR OWN RISK!

To verify whether we are hitting the PI, let's run the following query in the database: 1. SELECT server_identifier FROM push_notification_proxy_settings; LRpddSTgisziLG8jaO6S SELECT COUNT(*) FROM app_push_notification_queue WHERE push_content NOT LIKE "%XXX-XXX-XXX-XXX-XXXX%"; To remove old notifications: 1. run query: DELETE FROM app_push_notification_queue WHERE push_content NOT LIKE "%XXX-XXX-XXX-XXX-XXXX%"; 4hCCIaxyokaY1U1IvyC2 We should now be good to go and not seeing the errors in our logs any longer.