Skip to content
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

Not able to add torrent file via web interface since last release #1309

Open
UniverseXXX opened this issue Mar 17, 2023 · 9 comments · May be fixed by #1351
Open

Not able to add torrent file via web interface since last release #1309

UniverseXXX opened this issue Mar 17, 2023 · 9 comments · May be fixed by #1351
Labels
bug Something isn't working

Comments

@UniverseXXX
Copy link

Describe the bug
When adding a torrent file via web interface nothing happens.

To Reproduce
Steps to reproduce the behaviour:

  1. Click on + in the right low corner
  2. Click on the torrent file icon
  3. Select a torrent file from browser
  4. Nothing happens, no popup window appears as it used to be before

Platform:

  • OS: macOS, iOS, iPadOS
  • Browser: Safari, Chrome

Screenshot 2023-03-17 at 14 30 07

The above messages appear in the browser console log

@UniverseXXX UniverseXXX added the bug Something isn't working label Mar 17, 2023
@6c65726f79
Copy link
Owner

Have you tried to clear the cache by reloading the page with Cmd Shift R ?

@UniverseXXX
Copy link
Author

Have you tried to clear the cache by reloading the page with Cmd Shift R ?

Yep, tried that and also using a different browser and incognito sessions.

@arnauos
Copy link

arnauos commented Mar 27, 2023

Same here, rolling back to 1.7.1 fixes it.

I see this message in the browser console when I try to add a torrent:
Unhandled Promise Rejection: Error: no web crypto support

@bluskye
Copy link

bluskye commented Apr 3, 2023

Experiencing the same. Adding via URL is working

@apsoyka
Copy link

apsoyka commented Apr 21, 2023

Getting the same error on version 1.8.0; here's the log:

chunk-vendors.94715fc1.js:545 Uncaught (in promise) Error: no web crypto support
    at k (chunk-vendors.94715fc1.js:545:1354)
    at st (chunk-vendors.94715fc1.js:549:2098)
    at rt (chunk-vendors.94715fc1.js:549:396)
    at Object.parseBuffer (app.058545cd.js:1:65632)
    at Object.filesLoaded (app.058545cd.js:1:65483)
    at Object.readFiles (app.058545cd.js:1:65081)

@dlecan
Copy link

dlecan commented Apr 24, 2023

Same, Firefox, Chromium, Brave, when uploading a file

Uncaught (in promise) Error: no web crypto support
    k http://...js/chunk-vendors.94715fc1.js:545
    st http://...js/chunk-vendors.94715fc1.js:549
    rt http://...js/chunk-vendors.94715fc1.js:549
    parseBuffer http://...js/app.058545cd.js:1
    filesLoaded http://...js/app.058545cd.js:1
    readFiles http://...js/app.058545cd.js:1
    handleFiles http://...js/app.058545cd.js:1
    inputFile http://...js/app.058545cd.js:1
    inputFile http://...js/app.058545cd.js:1
    inputFile http://...js/app.058545cd.js:1
    5 http://...js/app.058545cd.js:1
    E http://...js/chunk-vendors.94715fc1.js:217
    a http://...js/chunk-vendors.94715fc1.js:217
    s http://...js/chunk-vendors.94715fc1.js:217
    s http://...js/chunk-vendors.94715fc1.js:217
    n http://...js/chunk-vendors.94715fc1.js:217
``

apsoyka added a commit to apsoyka/Transmissionic that referenced this issue May 18, 2023
Ignore VSCode Dev Container files.

Resolves 6c65726f79#1309, resolves 6c65726f79#1340
@apsoyka apsoyka linked a pull request May 18, 2023 that will close this issue
@remlio
Copy link

remlio commented Nov 14, 2023

same in safari. adding via url and magnet working fine

@remlio
Copy link

remlio commented Nov 15, 2023

hey folks, it’s working absolutely fine with ssl (https) connection. so you can set nginx server on reverse proxy to access transmission through https

@commonsons
Copy link

same here using edge and safari

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants