Sonarr version (exact version): Latest version
OS: Windows / Mac
Debug logs:
Description of issue:
It works on the machine thats running Sonarr but when I try to access else where when on my local net work I get this error
Safari can’t open the page “192.168.1.20:7979” because the server where this page is located isn’t responding.
and sometimes a bad reqest error. I dont know how to look at the logs so forgive me
How to get logs was right in the thread template when you created this https://wiki.servarr.com/sonarr/troubleshooting#logging-and-log-file
Additional Information:
- Information on the log files is here: Sonarr Troubleshooting | WikiArr
- Make sure debug logging is enabled in settings
- Post the log file, not a line or two, or just the error from the Logs table
- Post the full log to hone of the sites recommended in Logging and Log Files section of the wiki
- Do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document
Additionally, latest is not a version. Please always provide the number (and any other details as asked, like OS of the machine that is running Sonarr).
7979 is a non-standard port for Sonarr. Did you change it? You can check in Sonnar Settings > General
And is 192.168.1.20 the correct IP of the machine that is running Sonarr?
im running 2 instances of Sonarr one for animation and one for reg
Version
3.0.9.1549
.net Version
4.8.0
debug logs
2023-01-06 10:04:49.5|Debug|Api|[PUT] /api/v3/config/host: 202.Accepted (79 ms)
2023-01-06 10:04:49.5|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:04:49.5|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:04:50.0|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:04:50.1|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:04:59.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:04:59.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:04:59.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:04:59.6|Debug|Api|[GET] /api/v3/command: 200.OK (2 ms)
2023-01-06 10:05:18.2|Debug|Api|[GET] /api/v3/config/ui: 200.OK (1 ms)
2023-01-06 10:05:20.8|Debug|Api|[GET] /api/v3/health: 200.OK (4 ms)
2023-01-06 10:05:20.8|Debug|Api|[GET] /api/v3/system/status: 200.OK (29 ms)
2023-01-06 10:05:21.2|Debug|Api|[GET] /api/v3/diskspace: 200.OK (396 ms)
2023-01-06 10:06:32.1|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:06:32.2|Debug|Api|[GET] /api/v3/command: 200.OK (25 ms)
2023-01-06 10:06:32.2|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:06:32.2|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:07:03.5|Debug|Api|[GET] /api/v3/log/file: 200.OK (2 ms)
2023-01-06 10:08:00.2|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:08:00.2|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:08:00.2|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:08:00.2|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:08:24.8|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:08:24.8|Debug|Api|[GET] /api/v3/command: 200.OK (2 ms)
2023-01-06 10:08:54.7|Debug|InstallUpdateService|Checking for updates
2023-01-06 10:08:55.3|Debug|InstallUpdateService|No update available
2023-01-06 10:08:55.3|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:08:55.3|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:09:24.7|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:09:24.8|Debug|Api|[GET] /api/v3/system/status: 200.OK (30 ms)
2023-01-06 10:09:24.9|Debug|Api|[GET] /api/v3/diskspace: 200.OK (202 ms)
2023-01-06 10:09:27.4|Debug|Api|[GET] /api/v3/log/file: 200.OK (1 ms)
2023-01-06 10:09:32.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:09:32.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:09:32.5|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:09:32.5|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:10:58.6|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:10:58.6|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:10:58.6|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:10:58.6|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:11:01.4|Debug|Api|[GET] /api/v3/config/host: 200.OK (2 ms)
2023-01-06 10:11:01.9|Debug|Api|[GET] /api/v3/health: 200.OK (1 ms)
2023-01-06 10:11:01.9|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:11:01.9|Debug|Api|[GET] /api/v3/command: 200.OK (0 ms)
2023-01-06 10:11:01.9|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)
2023-01-06 10:11:36.9|Debug|Api|[GET] /api/v3/config/ui: 200.OK (0 ms)
2023-01-06 10:11:39.5|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-01-06 10:11:39.6|Debug|Api|[GET] /api/v3/system/status: 200.OK (36 ms)
2023-01-06 10:11:39.7|Debug|Api|[GET] /api/v3/diskspace: 200.OK (194 ms)
2023-01-06 10:11:40.7|Debug|Api|[GET] /api/v3/log/file: 200.OK (5 ms)
Are you able to access the other instance of sonarr? Or neither?
Also, make sure you have done per https://wiki.servarr.com/sonarr/faq#how-do-i-access-sonarr-from-another-computer
the other sonarr yes I can
I ran the animation sonarr as admin and still have the problem. the other sonarr doesnt work as well
I figured it out. I re-added the ports again and it works now
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.