Since last update nothing is working

[AxelHoss]

Hi, since your last update (Oktober 2nd) i cant view any cameras. Just when i open the app i can see my camera for a millisecond. Log doesnt say anything. Im the only one with this issue? Homepage working well

[piwko28]

Can you send some screenshots? What kind of device?

[AxelHoss]

[piwko28]

Thanks for sharing.
Currently I have no possibility to check it on Hyper OS.
Could you please clear app data (or uninstall and install again) and try to fill the settings again?
If it does not help - could you try to use demo server, just for test?

[AxelHoss]

Demo Server is working. Ive deleted the app an reinstalled. Nothing changed. Im the only one with this issue?

[piwko28]

I have no knowledge about similar issues.
Do you use authorization? Http or https?
I'll try to integrate an error reporting with next release to have better overview what happened.

[AxelHoss]

Http

[piwko28]

I made a test platform and it's working as intended. The error occurs when I provide wrong server data, in example password, but then nothing works including Storge info. Have you tried with other phone model? Any chance to share your Frigate instance for one day to check the reason? If so, please contact me via email.

[piwko28]

Just to be sure: did you left "path" completely empty?

[AxelHoss]

path is empty. Btw, the german translation here is wrong. Should be "Pfad" and not "Pfed".
Tried another hyperOs (have just hyperOs) and got the same issue. Whould you try it via wireguard?

[piwko28]

No, I haven't. Wireguard shouldn't have impact on it.
Thanks for the remark with the translation, it was corrected in newest release.

[gulo101]

I am experiencing the same issue. When I pull down to refresh, the cameras flash for a millisecond and then it's just a blank screen. There are no events either.

[piwko28]

I found an issue: Newly entered login credentials were only used after closing and reopening the app, not immediately after saving the settings. I fixed it in newest release 14.2.1, and it potentially fixes the issue. Please let me know if you still encounter the issue.

[gulo101]

I updated to 14.2.1 but still seeing the same issue.

[AxelHoss]

Same here

[piwko28]

I fixed an issue related to authorization for those who use self-signed certificates.

@AxelHoss you mentioned that your instance uses http though. Are you able to write an instruction how you configured authorization? I want to reproduce your case.

[AxelHoss]

I dont have to log in. There is no authoriztion

[pixielark]

Hi piwko28
I think the API access problem is caused by the auth token not attached to the request cookie properly (and make sure you are on the latest version of frigate when you test/debug this as this frigate change is pretty recent)

error log from frigate side

2024-10-19 10:21:10.560320071  172.19.0.121 - admin [19/Oct/2024:10:21:10 -0700] "GET /api/config HTTP/1.1" 401 179 "-" "okhttp/4.9.2" "2604:4080:redacted"

2024-10-19 10:21:10.603856482  172.19.0.121 - admin [19/Oct/2024:10:21:10 -0700] "GET /api/config HTTP/1.1" 401 179 "-" "okhttp/4.9.2" "2604:4080:redacted"

I do not see any log on frigate side that indicate the viewer is trying to retrieve auth token, so I checked the auth code here, and looks like there is no action from the viewer to call the frigate login API to retrieve the auth token and use it for all subsequent API access

entire auth workflow can be found here

My guess why you did not encounter the problem is because you are accessing port 5000 for API access but not 8971 which is guarded by auth? Or you are on early version of frigate

You will need to attach frigate_token in the cookie section of the request for API access to work. frigate_token is the default value according to the reference doc and it is configurable, which means you might need to add a section on UI to match it as well

and I would guess the cookie will need to be attached somewhere around here

hope this can help 😄

[piwko28]

@pixielark that helps a lot! I had no idea that Frigate introduced own authentication mechanism! I based on reverse proxy chapter, where they described basic auth - and the Frigate Viewer uses basic auth. Thanks for the remark, I'll analyze the Frigate authentication docs.

[piwko28]

Authorization is done and new version released.
Going back to original issue with no cameras:
@gulo101 which phone model and Android version do you use?

[gulo101]

Authorization is done and new version released. Going back to original issue with no cameras: @gulo101 which phone model and Android version do you use?

I am using Pixel 6 Pro. I was actually running Android 13 and last week I had to get a new phone (also Pixel 6 Pro) which came with Android 14. Same issue on both - the app opens, I see the thumbnails for last event for all the cameras for half a second, and then it just goes blank.

[MYeager1967]

I'm trying to connect through NGINX. What settings do I need to add where in order to get this to work? I have NGINX pointing to port 8971....

[gulo101]

Authorization is done and new version released. Going back to original issue with no cameras: @gulo101 which phone model and Android version do you use?

I think the issue was that my Frigate installation was old. I was still on 0.10. I just upgraded to 0.14 and I can see the cameras and recordings again. However now it does crash when I click on the "Settings" button.

[AxelHoss]

ok ur right. Update to the last frigate version solved the problem. Sorry for the trouble

[piwko28]

That's wonderfull news, @AxelHoss and @gulo101 ! Thanks for giving me know. I'll have a HyperOS for tests soon, but it seems that it wasn't an issue.

Version of the app is the supported Frigate NVR server version. Maybe I should consider to inform the user when it does not fit to avoid confusion.

@gulo101 try to clear app data or reinstall the app. Let me know if the problem still occurs.

[gulo101]

@gulo101 try to clear app data or reinstall the app. Let me know if the problem still occurs.

Reinstalling the app fixed it, everything is working now. Thanks!