Open CouldBeThis opened 3 weeks ago
Mika-
commented
1 week ago Network error should always be shown in all cases, but I will recheck this. Firefox has pretty long timeouts for some network errors and notification easily goes unnoticed when it's shown over a minute later. As for the symptoms that sounds like a hairpin nat and/or dns problem. Do things work when accessing normally via browser? Also it's worth cheking that hosts file doesn't have overrides.
CouldBeThis
commented
14 hours ago Do things work when accessing normally via browser?
Ah! OK you lead me to figure out the root cause in this instance:
I can visit the web interface in the browser but it requires clicking through confirmation to accept. I guess there is no way to do this in the extension. And accepting in the web interface doesn't transfer to the extension.
This probably explains the infrequency of the problem. I don't think most people have HTTPS-only turned on, and of those who do, many would probably also take the time to configure the certificate on their server. I'll also note that I am not using a real tld or domain name, just a fake local one, as that sometimes causes issues.
Workaround to fix the extension behavior: disable HTTPS-only for the domain.
Only mentioning in case it is useful in troubleshooting to somebody: the instructions in the link didn't work at first, I am not sure why
PR_END_OF_FILE_ERROR that cannot be bypassed, preventing access to the web GUI at all. (Which suggests it wasn't an issue of just mis-typing etc... it had some kind of effect.)about:config entry for browser.fixup.domainsuffixwhitelist.mynetworktld wasn't the source of the above. It's the fanciest DNS thing I have going on. (Not very fancy!) Doesn't seem to have any effect in any case. Hopefully this can help. The HTTPS issue itself is likely not worth the time to solve because it is probably a very narrow section who would have it. but there are likely other unusual situations causing disruptions (as suggested in above post) so a bit of hints that a problem exists and whatever is known regarding troubleshooting would be useful enough for anyone who has reason to use an extension like this.
Hi, thanks for the very useful and functional extension!
I am having the same issue described in #116. Adding torrent to qbittorrent fails silently. As suggested by @yazeed44, it was fixed by defining server by IP instead of domain.
If the actual underlying issue can't/won't be fixed, there should be a notice to the user to inform them of this. I only found the old issue by scrolling through issues related to qbittorrent. Some sort of error checking, note on the extension management page or whatever you feel is most appropriate.
In terms of actually resolving the issue, I have noticed something interesting which is that it actually works on a different device. Soo.. it isn't an issue with my server/network. (?)
device A: only works with IP Firefox developer 133.0b3 torrent-control 0.2.42
device B: works with domain name Firefox ESR 128.1esr torrent-control 0.2.42
Both are talking to the same server which is hosted on the LAN:
Is this problem common? I would expect more mentions of it if it were. Perhaps there is some idiosyncrasy of certain environments that causes this issue. I could try some troubleshooting like a clean new profile, firefox stable vs developer vs esr etc if it would be useful.