Subsonic Forum

When I share a song to facebook I get this http://198.111.223.46:90/share/RJcaB

Anyone know what is causing, and what fixes this?

It can be caused by permissions or transcoding errors. That error has also been associated with Flash problems.

Sharing had worked fine for years (or since it was available) and then a couple weeks ago I had to reinstall subsonic because the database got to be over 3GB and was corrupt. So what could be different that is causing this? It's the same machine, same permissions, etc.

I don't get this really. You're using jw-player 5.10 which indicates a fairly new or modded Subsonic, but your share refers to your file in the old Subsonic 4.6 style ("E:\Eric VanLandingham\Zombie Apocalypse\Zombie Apocalypse.mp3").

What version are you running?

I am running 4.7 (build 3106) – September 12, 2012, I just reinstalled a couple weeks ago.

Hopefully I can get this figured out this time.
Here's a share on my subsonic server
http://216.25.187.52:90/share/uQfVX
Notice it shows up but won't play.
However, if a user is logged in and browsing the subsonic interface, the song would play without issue.
Is this a problem with not being logged in? I am not thinking so, because even though I have closed the browser window I am still logged in, and that share won't work for me either.
It happens no matter what I try to share.

I have completely disabled the server firewall for testing and it makes no difference, and there is no indication of blocking in the firewall traffic log.

Try updating Flash, and install Adobe AIR also.

On the server?

Sent from my Nexus 4 using Tapatalk

Ok I updated flash and installed air on the server, no change.
Here is the error http://216.25.187.52:90/share/FeBdp

Are you still running 4.7? Try updating to 4.9, which I believe includes an updated jwplayer. That's where the error is coming from. I get the same 2032 error when I click your share links, but I know my adobe is updated to the most recent version.

No, it's already at 4.9

why are you running it over port 90?
That's the first thing that needs to be changed. You shouldn't be using ANY of the well known ports to run a personal program.

chickenbits wrote:why are you running it over port 90?
That's the first thing that needs to be changed. You shouldn't be using ANY of the well known ports to run a personal program.

What's wrong with port 90? Port scanners nowadays scan for any and all open ports.If the port fwd rule directs the request to the Subsonic host machine it will just get to the log on page.

I've fixed this error many times by using the older version of ffmpeg. Sometimes the new releases of ffmpeg wil also fix it. Sometimes it's a permissions issue. It's mostly about just finding the right combination that works. I don't think there's any single identifiable magic bullet for this problem.

I have a favorite ffmpeg version that handles video pretty well. If anyone requests it via pm I'll email it to them to try.

GJ51 wrote:

chickenbits wrote:why are you running it over port 90?
That's the first thing that needs to be changed. You shouldn't be using ANY of the well known ports to run a personal program.

What's wrong with port 90? Port scanners nowadays scan for any and all open ports.If the port fwd rule directs the request to the Subsonic host machine it will just get to the log on page.

I've fixed this error many times by using the older version of ffmpeg. Sometimes the new releases of ffmpeg wil also fix it. Sometimes it's a permissions issue. It's mostly about just finding the right combination that works. I don't think there's any single identifiable magic bullet for this problem.

I have a favorite ffmpeg version that handles video pretty well. If anyone requests it via pm I'll email it to them to try.

1. The well known ports list is for applications/services/ and processes registered with ICANN
2. Port scanners scan an IP address for open known ports. All well known ports are normally scanned.

This isn't a subsonic issue, this is a generic network issue with port 90. I mean I can't fix whatever the problem is, but I highly advise to get off the well known ports.

Also if it's linux only root can access ports lower than 1024. So if you've created a new user to run as subsonic on your machine, that could be a problem.

It doesn't matter what port its on, a port is a port. I'm a network security guy by trade, port 90 is forwarded to subsonic only, and it's clear as a bell on that path. The port is not the problem.