Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Cannot login on Android device #626

Open
IM-markus1909 opened this issue Jan 10, 2025 · 6 comments
Open

Bug: Cannot login on Android device #626

IM-markus1909 opened this issue Jan 10, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@IM-markus1909
Copy link

IM-markus1909 commented Jan 10, 2025

Is this urgent?

Yes

What parts are affected

Frontend

What is the server version

106

What is the client version

0.6.8

What platform are you using

Android

What's the problem 🤔

I cannot login using the Android App on my Galaxy S24.

After attempting a login, it reloads the login screen. It does not show any errors in the logs (see below) and a session token is created everytime I try to login. I'm connecting via Tailscale at the moment but I also tried it on my local network and via a Cloudflare Tunnel.

I'm using the All-In-One Unraid template https://codeberg.org/HanSolo97/unraid-templates#kitchenowl

Tried restarting the server and reinstalled the Android app. Didn't change anything.

Share your logs

[pid: 63|app: 0|req: 453/517] ::ffff:100.83.29.114 () {32 vars in 408 bytes} [Fri Jan 10 11:01:32 2025] POST /api/auth => generated 831 bytes in 876 msecs (HTTP/1.1 200) 2 headers in 72 bytes (3 switches on core 198)
[pid: 63|app: 0|req: 455/518] ::ffff:100.83.29.114 () {30 vars in 769 bytes} [Fri Jan 10 11:01:33 2025] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 72 bytes in 5 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 199)
[pid: 63|app: 0|req: 456/519] ::ffff:100.83.29.114 () {30 vars in 711 bytes} [Fri Jan 10 11:01:33 2025] GET /api/onboarding => generated 21 bytes in 12 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 199)

Share your configuration

No response

@IM-markus1909 IM-markus1909 added the bug Something isn't working label Jan 10, 2025
@topo03
Copy link

topo03 commented Jan 11, 2025

I experience the exact same issue.
I'm totally new to kitchenowl and just started today.
My setup:

  • kitchenowl AIO docker (latest) on OpenMediaVault (7.5.0-1)
  • old Intel-NAS with system-ssd + 2x 4TB HDD mirror
  • Android app (non-beta) from fdroid on Samsung Galaxy S23
  • both are version 0.6.8

Let me know if there is anything I can do, like testing or provide info.

Edit:
I have no problems logging in on iOS with an iPad.
I use HTTP only, not HTTPS ( On internal network only).

Update:
Now it works also in Android but only with the Google Play Store app.
Initially, I had tried with the FDroid app and had the log-in problems with that one.

Update II:
No, it doesn't work:
Meanwhile I discovered that I can actually log in from Android and iOS but will be logged out frequently. In fact, connection is so unstable that it is not usable as of now.

@IM-markus1909
Copy link
Author

Short update from me:

I switched back to a connection over Cloudflare Tunnel. Now it does seem to work again. Although the retrieval of items does seem to be very slow.

Can also report that my SO had severe problems with constant logging out as @topo03 wrote when using a connection over Tailscale in iOS, but it also does work now when using a CF Tunnel.

@Pontiac76
Copy link

I just found Kitchen Owl and have it self hosted. I've downloaded the Android app to my S24, but ran into issues logging in as well.

The thing is, and I should have realized this from the get-go, if you are running self hosted, you have to change to whatever FQDN you're running. Up until I started writing this exact post, I didn't realize that there was also a service offered by Kitchen Owl, so I found out the hard way I had to set what server I'm connecting to.

@IM-markus1909
Copy link
Author

The thing is, and I should have realized this from the get-go, if you are running self hosted, you have to change to whatever FQDN you're running.

Do you mean that a FQDN is always required? Haven't read that anywhere and it did work on my local network using the IP-address.

Also I encounterd another issue. When logged in (connected via Cloudflare Tunnel in this case) and my phone switched to standby mode, it dropped my connection then it took a few tries to log in again.

@Pontiac76
Copy link

No, if you're planning on staying internal, or use a VPN or something of the sorts, an IP address will work. In my case, I want my side exposed to the internet, so I specified the external FQDN in my connections. If you set the IP address, you're golden. If you're sitting on a LAN trying to connect, make sure your phone is on the LAN, and make sure that the machine you're hosting on doesn't have a firewall on, or, the ports are allowed in.

The point I was attempting to make is that in the app, on first install, I attempted to log into what I thought was my account on my server, but, the app is configured to go to its predefined site.

@topo03
Copy link

topo03 commented Jan 29, 2025

If you set the IP address, you're golden. If you're sitting on a LAN trying to connect, make sure your phone is on the LAN, and make sure that the machine you're hosting on doesn't have a firewall on, or, the ports are allowed in.

Nothing golden for me. Tried with internal only, no fw or other blocking, but connection kept dropping after a few seconds. Unusable...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants
@Pontiac76 @topo03 @IM-markus1909 and others