search

sp-engineering / frigate-viewer

GNU General Public License v3.0
12 stars 5 forks source link

Latest update getting JSON praise error #24

Open krishne35 opened 1 week ago

krishne35 commented 1 week ago

Screenshot_2024-10-10-21-21-48-41_01fc1bff8dd830c6a60eb317a0de2fc0.jpg

Have configured everything with password and username but getting unexpected character <

piwko28 commented 1 week ago

Similar issue to #23

The error occurs when wrong path, username or password were provided. Please double check it. Are you using http or https? Does the other tabs work, ie. Storage?

krishne35 commented 1 week ago

Https via traefik reverse proxy USERNAME and PASSWORD are correct

What am I supposed to fill in path?

piwko28 commented 1 week ago

Nothing. Maybe it's not clear enough.

So if your frigate GUI is under: https://frigate.local:5000 you should leave path empty.

But if it's in subdirectory: https://homeserver.local:5000/my_frigate the path should be "my_frigate"

Xaervyn commented 1 week ago

I am experiencing the same issue.

I am able to access Frigate through the web page using http://192.168.1.128:8971

However, when configuring the app with the same username and password, and the relevant protocol, IP address, and port, with path as empty, I am getting the same error as OP.

krishne35 commented 1 week ago

Nothing. Maybe it's not clear enough.

So if your frigate GUI is under: https://frigate.local:5000 you should leave path empty.

But if it's in subdirectory: https://homeserver.local:5000/my_frigate the path should be "my_frigate"

My path is simple

https://frigate.domain.com

The demo site works tho

piwko28 commented 1 week ago

New update introduces clear notification when username or password is incorrect. It should also provide anonymous debug info to better understand the issues (it may be disabled in settings), but probably it will not give helpful info for this particular case.

Would be perfect if anyone could provide a reverse proxy configuration or anything else to reproduce the issue.

krishne35 commented 1 week ago

New update introduces clear notification when username or password is incorrect. It should also provide anonymous debug info to better understand the issues (it may be disabled in settings), but probably it will not give helpful info for this particular case.

Would be perfect if anyone could provide a reverse proxy configuration or anything else to reproduce the issue.

Screenshot_2024-10-13-22-31-54-45_01fc1bff8dd830c6a60eb317a0de2fc0.jpg

So I'm running traefik as reverse proxy

IMG_20241013_223515.jpg

to-frigate: rule: "Host(xxxxxxx)" entryPoints:

frigate: loadBalancer: passHostHeader: true serversTransport: "pve" servers:

piwko28 commented 6 days ago

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.

Xaervyn commented 6 days ago

I'll try it out and let you know once it appears in the Play Store

krishne35 commented 6 days ago

No luck still same issue Uninstalled and reinstalled Manually typed the password still no luck

Xaervyn commented 6 days ago

Screenshot_20241014-230143 I'm getting a different error now, when using the same username and password I used for the Web version

Xaervyn commented 6 days ago

Oh, it might be something with my network setup. I'll check my firewall rules tomorrow. I can't access the webpage from my phone; only my desktop (different subnets)

krishne35 commented 6 days ago

Try https and see if it works

Oh, it might be something with my network setup. I'll check my firewall rules tomorrow.

Xaervyn commented 5 days ago

Try https and see if it works

Oh, it might be something with my network setup. I'll check my firewall rules tomorrow.

I disabled TLS in my Frigate configuration, because it doesn't work with Traefik, my Reverse Proxy, so that's why the direct-to-server address is http://192.168.1.128:8971.

I tested it again after enabling the firewall rule for 192.168.2.1/24 > 192.168.1.128:ANY traffic, and although I can now access the webpage from my phone through an internet browser, I'm still unable to connect the FrigateViewer app to my server. I'm receiving the error message "Wrong Credentials". I know the credentials are correct, because they're stored in Bitwarden. I did attempt to freetype the password just in case it was something weird with it autofilling the field, but I had the same results.

@krishne35 , are you still experiencing issues with the settings in the FrigateViewer app, or is it just me? When I checked the Play Store after you posted your comment yesterday, the app was still version 14.2.0, and the update for 14.2.1 wasn't yet available. I saw the update was posted to the Google Play store shortly before I posted my comment yesterday. You may need to go into the Play Store and update manually, if you haven't already.

piwko28 commented 4 days ago

Thanks for your input, especially @krishne35 . I reproduced the issue by installing Traefik. It seems that self-signed certificates were not accepted, while it's quite common for Frigate users. New version has been released with the fix.

I know @Xaervyn that you tried to use http and it also failed, but I have an impression that there are more than one case, which makes the issue harder to investigate.

Please let me know if there is still an issue after updating to 4.2.2.

krishne35 commented 4 days ago

Can you share the apk file coz it take a while to show up on playstore

krishne35 commented 4 days ago

Still no luck still getting wrong creds even with 14.2.2 Trued disabling tls and forward it directly to http on traefik yet wrong credentials

Xaervyn commented 4 days ago

I'm also still having issues on version 14.2.2 with "Wrong Credentials" when connecting to frigate using both the Traefik reverse proxy https address, as well as using the direct ip address with http protocol. I'm able to access both addresses from the browser on my phone without issue, so I'm almost certain [now] that it isn't a networking issue in my house.

piwko28 commented 3 days ago

Really weird. I have no more ideas. I need a broken environment to investigate it, or minimal reproducible example to create one.

piwko28 commented 3 days ago

I have one idea. I had to upgrad SDK from 33 to 34 (Android 14) - Google forced me, and one of the changes of new SDK is more restricted networking policy. It's strange that I have no issues with it. My phone has older Android, but I use emulator with new SDK. However, I'll try to fix it blindly and we'll see.

Xaervyn commented 3 days ago

Thank you. I am using a phone with Android 14, so that does sound like a possibility.

I found that Android 14 also automatically enables something called Private DNS, which will ignore the DNS servers provided to it by the DHCP server, and instead use cloudflare, google, or another provider. This was causing issues with me not being able to navigate to my Frigate server using Traefik. Unfortunately, turning this off did not correct the overall issue of it saying the credentials are wrong, but at least now I can connect without having to use the IP Address with HTTP, unfortunately just not in the FrigateViewer app.