2025-08-24, 11:59 PM
Safari is supported, the connection issues with localhost on macOS Safari can be due to system privacy settings or network controls rather than lack of Jellyfin compatibility. Adjusting permissions and clearing browser cache often fixes the problem.
Common causes and potential fixes to try:
Local Network Access Permission: macOS has a privacy setting for granting apps access to the Local Network. Make sure Jellyfin has permission to access the local network in:
System Settings > Privacy & Security > Local Network
Sometimes the app needs to be restarted after enabling this.
Firewall or Network Configuration: Ensure no firewall or security software is blocking connections on port 8096 for localhost.
Try Explicit Protocol: In Safari, try entering the URL as http://localhost:8096 (including the "http://") instead of just localhost:8096.
Test on Another Browser: Since Chrome works fine, the issue is definitely related to how Safari handles local connections, possibly caching or cookie/session issues. Trying to clear Safari's cache or disabling extensions that could block local connections might help.
Multiple Jellyfin Processes: On macOS, sometimes only one instance of Jellyfin is running or the server process may not be fully started. Check the Activity Monitor for Jellyfin processes.
Common causes and potential fixes to try:
Local Network Access Permission: macOS has a privacy setting for granting apps access to the Local Network. Make sure Jellyfin has permission to access the local network in:
System Settings > Privacy & Security > Local Network
Sometimes the app needs to be restarted after enabling this.
Firewall or Network Configuration: Ensure no firewall or security software is blocking connections on port 8096 for localhost.
Try Explicit Protocol: In Safari, try entering the URL as http://localhost:8096 (including the "http://") instead of just localhost:8096.
Test on Another Browser: Since Chrome works fine, the issue is definitely related to how Safari handles local connections, possibly caching or cookie/session issues. Trying to clear Safari's cache or disabling extensions that could block local connections might help.
Multiple Jellyfin Processes: On macOS, sometimes only one instance of Jellyfin is running or the server process may not be fully started. Check the Activity Monitor for Jellyfin processes.