If you are getting iframe errors with the new rutorrent, or a new deployment of rutorrent, read here. #2862
sporked-thm
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Fixing ruTorrent "contentDocument is null" & Iframe 404 Errors in Nginx
Issue:
When submitting a torrent in ruTorrent, you may see errors like:
"contentDocument is null"
"GET /<rutorrent_dir_goes_here>/php/addtorrent.php 404 (Not Found)"
or in my case it was, when adding an upload
-'"Uncaught TypeError: Cannot read properties of null (reading 'href') "'
This happens because Nginx is not correctly handling PHP files inside
<rutorrent_dir_goes_here>/php/
.Step-by-Step Fix
1: Edit Nginx Configuration**
Open your Nginx config file:
Or, if ruTorrent has a separate config, open it:t
2: Add the Correct Location Block to your config file**
Find your
server {}
block and add/update these sections:in my case, nginx
server {
listen 80;
server_name my.domain; # Change this to your actual domain
}
3: Test and Apply the Fix**
Check for errors:
Restart Nginx & PHP 8.1-FPM:
4: Verify Fix**
Open a browser and visit:
https://my.domain/<rutorrent_dir_goes_here>/php/addtorrent.php
Now, ruTorrent should work without errors, and iframe uploads will process correctly!
Beta Was this translation helpful? Give feedback.
All reactions