failing to load repository - connection issue #43

Open
opened 2 months ago by chendu · 9 comments
chendu commented 2 months ago

Looks like it can't connect, verified its not my network as tried with VPN and mobile data.

From the toast it says can't connect to f-droid.org/<IP address) but not sure why it would be going to a URI which contains an IP. See screenshot

Thanks

Looks like it can't connect, verified its not my network as tried with VPN and mobile data. From the toast it says can't connect to f-droid.org/<IP address) but not sure why it would be going to a URI which contains an IP. See screenshot Thanks
Owner

I don't think it's the URI in the error message, but hostname/IP (Port).

At the same time you could open the f-droid webpage with a browser on your device?

I don't think it's the URI in the error message, but hostname/IP (Port). At the same time you could open the f-droid webpage with a browser on your device?
Poster

Thanks for the fast response. Perhaps in the next version you could put the IP in brackets in the toast notification for clarity.

The running.json seems to work on same device & same network when opened in the browser. See attached images.

Thanks

Thanks for the fast response. Perhaps in the next version you could put the IP in brackets in the toast notification for clarity. The running.json seems to work on same device & same network when opened in the browser. See attached images. Thanks
Owner

The error message is from the underlying http library. But I'll have look if I can improve it.

The error message is from the underlying http library. But I'll have look if I can improve it.
Poster

I also turned off private DNS to rule that out but still not working.

I also turned off private DNS to rule that out but still not working.
pstorch self-assigned this 2 months ago
pstorch added the
enhancement
label 2 months ago
Poster

Ah I see regarding the library, that's no problem just thought I'd mention it.

The app was working before, i also tried clearing storage and cache.

Any idea what could be causing it? Ruling out a network issue.

Ah I see regarding the library, that's no problem just thought I'd mention it. The app was working before, i also tried clearing storage and cache. Any idea what could be causing it? Ruling out a network issue.
Owner

Have you tried force stopping the app? Maybe hostname IP resolution is cached.

Have you tried force stopping the app? Maybe hostname IP resolution is cached.
Poster

Yes I've tried this, the app was working for me before, maybe 4 months ago.

Could it be the OS interfering? I wouldn't think so but it seems like a strange problem.

Im guessing the app is doing a simple pull of the json files then just filtering the output. Seems strange that I can browse to the .json fine but it fails when using the app.

Doubtful, but is there any google/play services dependencies?

Yes I've tried this, the app was working for me before, maybe 4 months ago. Could it be the OS interfering? I wouldn't think so but it seems like a strange problem. Im guessing the app is doing a simple pull of the json files then just filtering the output. Seems strange that I can browse to the .json fine but it fails when using the app. Doubtful, but is there any google/play services dependencies?
Owner

Could it be the OS interfering? I wouldn't think so but it seems like a strange problem.

It must be, because in the app I "just" call the URL with the hostname. So the DNS resolution is done by the device.

I'm not sure why the browser can access the f-droid server.

Doubtful, but is there any google/play services dependencies?

No, that wouldn't be possible with an build by F-Droid.

Last idea: device reboot. I know it's a lame solution.

> Could it be the OS interfering? I wouldn't think so but it seems like a strange problem. It must be, because in the app I "just" call the URL with the hostname. So the DNS resolution is done by the device. I'm not sure why the browser can access the f-droid server. > Doubtful, but is there any google/play services dependencies? No, that wouldn't be possible with an build by F-Droid. Last idea: device reboot. I know it's a lame solution.
Owner

@chendu is it still failing?

@chendu is it still failing?
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.