-
Notifications
You must be signed in to change notification settings - Fork 15
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
No torrents #74
Comments
Yeah I didn't test deluge 1 at all with the recent version. Did the
previous version work?
…On Tue, Jan 2, 2024, 07:45 VatraXD ***@***.***> wrote:
Hi!
The app looks great, but I don't see my torrents running. I can add them
and they show up on the desktop client, but not on the phone.
The download and upload speed also work. Plus in the filtering menu I do
see my trackers, so its kinda working? The torrents just won't show and it
says no torrents. Maybe because my server is on version 1.3.15? Thanks!
—
Reply to this email directly, view it on GitHub
<#74>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHCHNPLBPP5IWCNJMXI3ZK3YMNUS7AVCNFSM6AAAAABBJO7W22VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DCOBXG43TMMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I'm a new user, I don't know. Give me a few moments and I'll check. Weird that it connects but torrents wont show. |
Yes, with app version 1.3.0 it shows the torrents. |
I am having a similar issue, and not sure if it is related. The logs that I see on the client side when this happens are below. Adding if that helps.
App version: 1.4.1 |
Version 1.4.3 released with fix for Deluge 1 connection > empty list on open. |
Hi!
The app looks great, but I don't see my torrents running. I can add them and they show up on the desktop client, but not on the phone.
The download and upload speed also work. Plus in the filtering menu I do see my trackers, so its kinda working? The torrents just won't show and it says no torrents. Maybe because my server is on version 1.3.15? Thanks!
The text was updated successfully, but these errors were encountered: