Unable to connect (network error occured) since last update

[draccas]

Hello,

I'm using Ultrasonic with an Airsonic server.
Everything worked well, but since last update I can't connect anymore.
I have the following error message when using "Test Connection":

Connection failure. A network error occured. Please check the server address or try again later

And same when trying to get arsits:

A network error occured. Please check the server address or try again later.

I watch the log in my server but nothing: Ultrasonic seems no connect.
I also try to go on server URL from my Android and works good.

Did you make a change that can explain that?
Thanks in advance.

[ogarcia]

@draccas

Please can you provide more info?

System information

• Ultrasonic version: version of the app
• Android version: Version of Android OS on the device
• Device info: Device manufacturer, model

Are you using HTTPS with self-signed certificate? In this case you must select the Allow self-signed HTTPS certificate option.

Other cause is that you must write protocol in the URL, if your server is example.com you must set it as http://example.com

[paddatrapper]

Chiming in here because I have the same issue, also using airsonic.

System information

Ultrasonic version: 2.1.0
Android version: 7.0
Device info: Samsung J5 Pro (SM-J530F)

I am using a LetsEncrypt certificate and other clients (both web-browsers and the subsonic android app) connect with no issues. I have the https protocol in the URL.

[Tapchicoma]

Hm, I am also using Airsonic with Let's encrypt certificate and everything works ok 🤔

[Tapchicoma]

What Airsonic version are you using?

[paddatrapper]

10.1.1-RELEASE on Debian stable behind a nginx proxy (LXC containers if that makes a difference)

[Tapchicoma]

Ok, almost same for me - 10.1.1-RELEASE – December 16, 2017 using docker image behind nginx proxy.

Seems app need a way to collect request-response logs and save it locally, so it can be attached to issue.

[draccas]

Thanks for your response.

Are you using HTTPS with self-signed certificate? In this case you must select the Allow self-signed HTTPS certificate option.

Sorry, I can't find this option. Where is it?

I do not use Let's encrypt. My certificate is self signed.

Ultrasonic version: 2.0.0 (from F-Droid)
Android version: 7.0.1 (Lineage OS)
Device info: OnePlus 3
Airsonic version: 10.1.1 + nginx proxy from Airsonic documentation.

This is an awesome app. Thanks for your help.

[ogarcia]

Sorry, I can't find this option. Where is it?

With latest version (2.1.0). Into server settings, between enabled and jukebox options.

@paddatrapper If you check the Allow self-signed HTTPS certificate persists the issue?

[draccas]

Unfortunately the version is not up to date in F-Droid and I have not the Play Store on my phone.
Can you update you app in this repository please?

I thinks this probably fix the bug, because as I say I have no trace in Airsonic log when trying to connect with Ultrasonic.

[paddatrapper]

@paddatrapper If you check the Allow self-signed HTTPS certificate persists the issue?

Uninstalling and re-installing the app fixed the issue for me

[Tapchicoma]

@paddatrapper you maybe affected by your issue: airsonic/airsonic#676. I've just have same on test env.

#121 - in next version app will show better errors messages

[ogarcia]

@draccas if you are using the FDroid then download version 1.8, because they have problems with the build servers and the version 2.1.0 is not available.

There is an issue open for this cause in https://gitlab.com/fdroid/fdroiddata/issues/1053

[draccas]

@ogarcia Thanks it works on 1.8.
Hope F-Droid will resolve their problems.

[ogarcia]

@draccas we update client with several enhancements but unfortunately F-Droid people still have issues with they build servers. I recommend you download our latest apk build 2.2.0 from our repo and tell us if work as expected. Take note that the certificate that signs the akp is not the same because F-Droid use his own certificate.

[ogarcia]

New issue open in F-Droid because no new builds https://gitlab.com/fdroid/fdroiddata/issues/1107

[Tapchicoma]

We removed versioning plugin that causes the problems to build of F-Droid, but it is not yet merged into master. F-Droid should build next release.

[Tapchicoma]

@draccas 2.1.0 is available on F-Droid. Can you check again?

[ogarcia]

Latest release is now in F-Droid, we can close this issue.