Permission Denied on all pages after upgrading to 1.4.4 from 1.3.77 #4299
Comments
|
Is |
|
Just to verify, I checked the environment variables in the pod and I did notice what seems to be a |
|
|
{
"is_installed": true,
"token_ok": true,
"allow_signup": true,
"is_user_anonymous": false,
"license": "OpenSource",
"version": "1.4.4",
"recaptcha_site_key": "redacted",
"currently_undergoing_maintenance_message": null,
"api_url": "https://metrics.sand.redacted/"
}The only thing that may be interesting is that the {
"pk": "redacted",
"organization": {
"pk": "redacted",
"name": "Self-Hosted Organization"
},
"current_team": null,
"email": "kogan@redacted",
"username": "kogan@redacted",
"name": "Kogan, Ilya",
"role": 0,
"avatar": "/avatar/redacted",
"avatar_full": "https://metrics.sand.redacted/avatar/redacted",
"timezone": "America/Detroit",
"working_hours": {
"monday": [
{
"start": "09:00:00",
"end": "17:00:00"
}
],
"tuesday": [
{
"start": "09:00:00",
"end": "17:00:00"
}
],
"wednesday": [
{
"start": "09:00:00",
"end": "17:00:00"
}
],
"thursday": [
{
"start": "09:00:00",
"end": "17:00:00"
}
],
"friday": [
{
"start": "09:00:00",
"end": "17:00:00"
}
],
"saturday": [],
"sunday": []
},
"unverified_phone_number": null,
"verified_phone_number": null,
"slack_user_identity": null,
"telegram_configuration": null,
"messaging_backends": {
"MOBILE_APP": {
"connected": false
},
"MOBILE_APP_CRITICAL": {
"connected": false
},
"EMAIL": {
"email": "kogan@redacted"
}
},
"notification_chain_verbal": {
"default": "Email",
"important": "Email"
},
"cloud_connection_status": 1,
"hide_phone_number": false,
"has_google_oauth2_connected": false,
"is_currently_oncall": false,
"google_calendar_settings": null,
"rbac_permissions": []
}The calls to the following all return 403s:
All of these are rooted at |
|
This is strange the /status endpoint uses the info from the plugin to authenticate so Grafana -> OnCall should be ok. Testing OnCall -> Grafana can be tested by trying the following:
You should see a response something like this: This should tell us if the URL OnCall is using to talk to Grafana and the token are ok |
|
Yup, I'm seeing generally that, except obviously the url is different: |
|
This has mysteriously been fixed in 1.4.7, thanks for all of your help! |
What went wrong?
What happened:
What did you expect to happen:
How do we reproduce it?
It's hard to determine how to reproduce this issue given it occurred after an upgrade.
Grafana OnCall Version
v1.4.4
Product Area
Auth, Helm, Other
Grafana OnCall Platform?
Kubernetes
User's Browser?
Microsoft Edge 124.0.2478.51
Anything else to add?
root_url.Note that I've tried removing the list of allowed IPs which is currently set to the node public IP range and get the same result.
Is there a way to enable deeper debugging?
The text was updated successfully, but these errors were encountered: