Permissions and HTTPS

[theRSebURNTE]

Hello, I just downloaded subsonic and it seems to be exactly what I need to share music without going through spotify and the such.

I have encountered two issues.

First of all, I have two folders which I want to share, but not with everyone. The users for now are myself (A) and another one (B). My first issue is that when I unselect a folder in B's permissions list, it can indeed see the files from only that folder (and subfolders), but when B try to click a folder, an album or play songs, it brings B to a page which says "Sorry, you are not authorized to perform the requested operation."

It seems to be a bug since B has the permissions required to play songs and access those folders.

I made several test users and the problem really arise when I remove access to one of the two folders.


My second issue is when I try enabling https on port 4443. When I try accessing the server (after duly resetting it), chrome (and other browsers) say it's unsecured (the https sign has a red crossed diagonal).

Any help would be appreciated.

[acroyear]

Just turning on the built-in https uses a 'self-signed' certificate, which browsers consider to be inherently risky. In some cases you can make an exception and accept it anyways, in others you can't. It causes problems with html5-based apps (like SubFire) that are packaged for Android or IOS, in that you can't make an exception for self-signed and the platform will refuse to connect.

The proper solution is to have your own domain and purchase a certificate signed by a trusted certificate authority.

[theRSebURNTE]

Thanks, although I have no clue how domains and certificates work....

Do I only need a domain name or do I need to pay for a web hoster as well? Also, how much does a certificate cost?

Also, what about the first issue?

Thanks for your help!