Latest update getting JSON praise error

[krishne35]

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

[piwko28]

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]

Https via traefik reverse proxy
USERNAME and PASSWORD are correct

What am I supposed to fill in path?

[piwko28]

Nothing. Maybe it's not clear enough.
[protocol]://[host]:[port]/[path]

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]

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]

Nothing. Maybe it's not clear enough.
[protocol]://[host]:[port]/[path]

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]

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]

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.

So I'm running traefik as reverse proxy

to-frigate:
rule: "Host(xxxxxxx)"
entryPoints:
- websecure
tls:
certResolver: cloudflare
service: frigate

frigate:
loadBalancer:
passHostHeader: true
serversTransport: "pve"
servers:
- url: https://100.0.0.7:8971
serversTransports:
pve:
insecureSkipVerify: true

[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.

[Xaervyn]

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

[krishne35]

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

[Xaervyn]

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

[Xaervyn]

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]

Try https and see if it works

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

[Xaervyn]

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]

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]

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

[krishne35]

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]

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]

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

[piwko28]

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]

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.

[ItsMeMegaMind]

@piwko28 Sorry for hijacking this thread. I can see you have added support for frigate authentication. Will it be possible to release a new apk. I tried compiling myself but i could only generate the debug one not the release one.

[piwko28]

I'll push new update soon. Unfortunately I'm not able to share an apk file here, because it's much heavier than Play store update. The work is still in progress.

[piwko28]

@ItsMeMegaMind the changes will be available for beta testers soon, probably today. It contains changes which affects the whole application, so I need to perform regression tests before publishing. If you wish to try it, sign up to beta testers program (should be available on application page in Play store).

[ItsMeMegaMind]

@piwko28 I just signed up for the beta and installed the update. Worked like a charm. Thank you.

[piwko28]

Great, nice to hear! Anyone else can test it? @Xaervyn , @krishne35 ?

[piwko28]

@ItsMeMegaMind is event payback working at your side (when you click one on events list)?

[krishne35]

Can login fine now but when I select any event it force closes

[ItsMeMegaMind]

It's the same thing on mine too. It logs in and does live streams fine but opening an event crashes the app.

[piwko28]

Ok, thanks, same on my side. But it's the only bug that I found. I'm not able to fix it today, I'll release fixed version on Monday.

[piwko28]

New version has been released and should be available publicly for all users.

[Xaervyn]

Sorry, I was out of town when you posted this, and was unable to test within my local environment. I returned today, and it is working great. Thank you so much!

[krishne35]

New version has been released and should be available publicly for all users.

ALL mentioned errors were fixed with new version
Thank you :)