[GH-ISSUE #381 ] [Bug] Network Request Failed #247

Author

Owner

@MohamedBassem commented on GitHub (Sep 9, 2024):

No this is unlikely to be a password issue. This is usually the server address being unreachable from the phone or incorrectly setup (e.g invalid certs).
Can you tell us if you're using http/https, is Hoarder behind a reverse proxy? Any special setup there?

@MohamedBassem commented on GitHub (Sep 9, 2024): No this is unlikely to be a password issue. This is usually the server address being unreachable from the phone or incorrectly setup (e.g invalid certs). Can you tell us if you're using http/https, is Hoarder behind a reverse proxy? Any special setup there?

kerem commented

Author

Owner

@marco-studer-srf commented on GitHub (Sep 9, 2024):

The server is behind traefik reverse proxy. The server is using https with a self-signed certificate. The root certificate is added as CA on the phone. Could this be a problem?

@marco-studer-srf commented on GitHub (Sep 9, 2024): The server is behind traefik reverse proxy. The server is using https with a self-signed certificate. The root certificate is added as CA on the phone. Could this be a problem?

kerem commented

Author

Owner

@hubono commented on GitHub (Sep 9, 2024):

Hi
I'm having the same issue. I installed hoarder on oracle free tier. All went ok.
I installed the app on Android and it's working good.
Now I installed on iphone, made a new user thought the web browser on the iphone, inputted the same details on the app and i get network request failed. I tried on the wifi and 5g, both fail. Im using http

@hubono commented on GitHub (Sep 9, 2024): Hi I'm having the same issue. I installed hoarder on oracle free tier. All went ok. I installed the app on Android and it's working good. Now I installed on iphone, made a new user thought the web browser on the iphone, inputted the same details on the app and i get network request failed. I tried on the wifi and 5g, both fail. Im using http

kerem commented

Author

Owner

@CrypticC3s4r commented on GitHub (Sep 10, 2024):

Having the same issue with Android,
It is behind a nginx reverse proxy.

Extension access and Direct Access are functioning well, just mobile makes the problem.

@CrypticC3s4r commented on GitHub (Sep 10, 2024): Having the same issue with Android, It is behind a nginx reverse proxy. Extension access and Direct Access are functioning well, just mobile makes the problem.

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Sep 10, 2024):

I'll release a hoarder mobile update soon that hopefully can help us debug those network connection issues and show exactly the kind of errors that are being reported.

@MohamedBassem commented on GitHub (Sep 10, 2024): I'll release a hoarder mobile update soon that hopefully can help us debug those network connection issues and show exactly the kind of errors that are being reported.

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Sep 14, 2024):

I've sent (github.com/hoarder-app/hoarder@3452e47c94) to add a new "Test connection" page to debug server connection issue. I hope this help figure out why the app is not working for you. I've submitted this to apple/google for review, should hopefully be available for download by Monday.

@MohamedBassem commented on GitHub (Sep 14, 2024): I've sent (https://github.com/hoarder-app/hoarder/commit/3452e47c94a55a525620c244f57edb9482989d1c) to add a new "Test connection" page to debug server connection issue. I hope this help figure out why the app is not working for you. I've submitted this to apple/google for review, should hopefully be available for download by Monday.

kerem commented

Author

Owner

@marco-studer-srf commented on GitHub (Sep 16, 2024):

Running connection test ...
Using address: https://xxx
Network connection failed: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Okay, it seems to be the certificate. However, I added the certificates to the root certificates of the phone. Accessing Hoarder via browser on the phone is working.

@marco-studer-srf commented on GitHub (Sep 16, 2024): > Running connection test ... Using address: https://xxx Network connection failed: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. Okay, it seems to be the certificate. However, I added the certificates to the root certificates of the phone. Accessing Hoarder via browser on the phone is working.

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Sep 16, 2024):

@marco-studer-srf Glad to see the new connection debugging thing being useful! Let's change the issue title to be about self signed certs then. I'll check if there's any configuration I need to pass to the app manifest so that it can pick up all of your trusted certs (most likely over the weekend).

@MohamedBassem commented on GitHub (Sep 16, 2024): @marco-studer-srf Glad to see the new connection debugging thing being useful! Let's change the issue title to be about self signed certs then. I'll check if there's any configuration I need to pass to the app manifest so that it can pick up all of your trusted certs (most likely over the weekend).

kerem commented

Author

Owner

@chrishoage commented on GitHub (Oct 14, 2024):

I am experiencing this issue using http - I get the same error

Network connection failed: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Except that I'm using http specifically, and the debug output indicates this.

Is the app trying to upgrade to an https connection?

If so - then I'm hitting the same self signed cert error - however I do not wish to add this cert to the root certificates of my phone.

Can there be an option to allow self signed certs?

@chrishoage commented on GitHub (Oct 14, 2024): I am experiencing this issue using http - I get the same error > Network connection failed: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. Except that I'm using `http` specifically, and the debug output indicates this. Is the app trying to upgrade to an https connection? If so - then I'm hitting the same self signed cert error - however I do not wish to add this cert to the root certificates of my phone. Can there be an option to allow self signed certs?

kerem commented

Author

Owner

@marco-studer-srf commented on GitHub (Dec 12, 2024):

@MohamedBassem In one of my own projects, I happened to face the same issue. Adding the following network security config to the application makes it accept user-added CAs. It also allows cleartext traffic (http), since self-hosters will usually go one of these two ways.

In res/xml/network_security_config.xml:

<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
    <base-config cleartextTrafficPermitted="true">
        <trust-anchors>
            <certificates src="system" />
            <certificates src="user" /> <!-- this is the part that makes it work -->
        </trust-anchors>
    </base-config>
</network-security-config>

And in your manifest, add:

android:networkSecurityConfig="@xml/network_security_config"
android:usesCleartextTraffic="true"

@marco-studer-srf commented on GitHub (Dec 12, 2024): @MohamedBassem In one of my own projects, I happened to face the same issue. Adding the following network security config to the application makes it accept user-added CAs. It also allows cleartext traffic (http), since self-hosters will usually go one of these two ways. In `res/xml/network_security_config.xml`: ```xml <?xml version="1.0" encoding="utf-8"?> <network-security-config> <base-config cleartextTrafficPermitted="true"> <trust-anchors> <certificates src="system" /> <certificates src="user" />  </trust-anchors> </base-config> </network-security-config> ``` And in your manifest, add: ```xml android:networkSecurityConfig="@xml/network_security_config" android:usesCleartextTraffic="true" ```

kerem commented

Author

Owner

@Raizel-thebloodstorm commented on GitHub (Jan 1, 2025):

Bro where to add what ...please explain a little more

@Raizel-thebloodstorm commented on GitHub (Jan 1, 2025): Bro where to add what ...please explain a little more

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Jan 1, 2025):

@Raizel-thebloodstorm this is going to be fixed in the next mobile app release. You won't be able to fix it yourself.

@MohamedBassem commented on GitHub (Jan 1, 2025): @Raizel-thebloodstorm this is going to be fixed in the next mobile app release. You won't be able to fix it yourself.

kerem commented

Author

Owner

@Ciucci666 commented on GitHub (Jan 19, 2025):

I had the same problem, i solved it just by adding the https:// and then it worked

@Ciucci666 commented on GitHub (Jan 19, 2025): I had the same problem, i solved it just by adding the `https://` and then it worked

kerem commented

Author

Owner

@jnskender commented on GitHub (Jan 19, 2025):

I had the same problem, i solved it just by adding the https:// and then it worked

Also fixed my issue.

@jnskender commented on GitHub (Jan 19, 2025): > I had the same problem, i solved it just by adding the `https://` and then it worked Also fixed my issue.

kerem commented

Author

Owner

@ClausMunch commented on GitHub (Jan 26, 2025):

I had the same problem, i solved it just by adding the https:// and then it worked

Came here for the cake. This helped! :)

@ClausMunch commented on GitHub (Jan 26, 2025): > I had the same problem, i solved it just by adding the `https://` and then it worked Came here for the cake. This helped! :)

kerem commented

Author

Owner

@l3s2d commented on GitHub (Feb 2, 2025):

I'm still seeing this issue on mobile app version 1.6.7 with a self-signed certificate.

@l3s2d commented on GitHub (Feb 2, 2025): I'm still seeing this issue on mobile app version 1.6.7 with a self-signed certificate.

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Feb 2, 2025):

I have submitted the release to google yesterday with the fix. Hopefully it'll be out in a couple of days.

@MohamedBassem commented on GitHub (Feb 2, 2025): I have submitted the release to google yesterday with the fix. Hopefully it'll be out in a couple of days.

kerem commented

Author

Owner

@aia832003 commented on GitHub (Feb 3, 2025):

Thanks for the update @MohamedBassem is the apk available for those that would like manually install before the Play Store?

@aia832003 commented on GitHub (Feb 3, 2025): Thanks for the update @MohamedBassem is the apk available for those that would like manually install before the Play Store?

kerem commented

Author

Owner

@MohamedBassem commented on GitHub (Feb 5, 2025):

The update is live on the play store. Please give it a try and let me know how it goes

@MohamedBassem commented on GitHub (Feb 5, 2025): The update is live on the play store. Please give it a try and let me know how it goes

kerem commented

Author

Owner

@l3s2d commented on GitHub (Feb 5, 2025):

Working for me now, thank you!

@l3s2d commented on GitHub (Feb 5, 2025): Working for me now, thank you!

kerem commented

Author

Owner

@aia832003 commented on GitHub (Feb 5, 2025):

GM @MohamedBassem even after the latest update, I'm getting network request failed on my reverse proxy setup via android app. Was working previously and can reach it on my same device via browser. Also seems to work on my iOS devices just fine. Any suggestions?

"Network connection failed: Failed to connect to"

@aia832003 commented on GitHub (Feb 5, 2025): GM @MohamedBassem even after the latest update, I'm getting network request failed on my reverse proxy setup via android app. Was working previously and can reach it on my same device via browser. Also seems to work on my iOS devices just fine. Any suggestions? "Network connection failed: Failed to connect to"

kerem commented

Author

Owner

@hermann1514 commented on GitHub (Apr 8, 2025):

Same for me.
Login with App: "Network connection failed: Failed to connect to"
With Brwoser from the same IOS device the login is working.

@hermann1514 commented on GitHub (Apr 8, 2025): Same for me. Login with App: "Network connection failed: Failed to connect to" With Brwoser from the same IOS device the login is working.

kerem commented