apognu / otter

Music player for Funkwhale
MIT License
214 stars 21 forks source link

Login not working on WiFi #116

Open a20eac1d opened 3 years ago

a20eac1d commented 3 years ago

Describe the bug

I have setup a Funkwhale instance and want to use Otter to connect to it via insecure HTTP. I have entered the login details and click on connect. When I am connected to a WiFi network the app doesn't work. A message pops up saying "Logging in" for a split second and then disappears without any other notice. I'm stuck on the login screen. Switching to 4G mobile data makes it work again and I can listen to music. Switching back to WiFi and refreshing makes all the albums and songs disappear.

In about 5% of all logins I get an error message under the host name text field saying:

_"java.lang.IllegalStateException: Expected BEGINOBJECT but was STRING at line 1 column 1 path $"

This is a Gist with the logcat output, but there is nothing interesting

https://gist.github.com/a20eac1d/b299e5d4546ccf5d3527057189c00dbe

How to reproduce

  1. Try to login via WiFi
  2. It doesn't work

Expected behavior

It should work with any kind of internet connection.

Environment details

a20eac1d commented 3 years ago

By monitoring my nginx access logs it seems like no traffic is hitting the web server at all.

So Otter doesn't want to connect with these settings on WiFi for some reason, but it works on 4G mobile data:

AMoonRabbit commented 3 years ago

So to confirm, whilst on your WiFi, if you browse to http://yourip you get your Funkwhale instance Web UI served?

s-ol commented 1 year ago

I'm having this issue with Funkwhale 1.2.9 and a (multi-container) docker setup, no matter what type of connection I use on my phone. Each time I hit login, the funkwhale API container logs this message:

2023-01-22 14:14:41,048 django.request WARNING  Not Found: /api/v1/token/

When I do a login from the web interface, it doesn't use that endpoint, but instead POSTs to /api/v1/users/login, did the API schema change?