bliss is designed as a server application, to run in the background, presenting a Web UI through which you access its various features (on Windows, this appears to work like a usual foreground app, but in reality bliss is still running a background Web server, so this FAQ still applies). As a result it requires certain ports to be open on its host, so that external clients can make connections.
By default, there are two ports that must be opened:
Port 3220 is used to serve the Web UI. Port 3221 is also used by bliss's internal web server, exclusively for delivering debug related information as required.
On rare occasions, if another piece of software has already taken the ports bliss uses by default, it is necessary to change the port numbers so bliss's web pages can be seen.
The first way of configuring which port to run on is to look for a file called
config in the following location:
|Windows XP||C:\Documents and Settings\[username]\.bliss|
|Windows Vista, 7, 8 and 10||C:\Users\[username]\.bliss|
|Mac OS X (see below)||/Users/[username]/Library/Preferences/bliss|
|QNAP||`getcfg SHARE_DEF defVolMP -f /etc/config/def_share.info`/.qpkg/bliss/.bliss|
If there's no such file there, create one.
Next, we need to make sure the following lines are in the file:
These change the web UI and debug UI ports to 5220 and 5221 respectively. You can leave either line out; in which case the default port is used for the line that is removed.
You must restart bliss after changing the file.
An alternative exists, and that is to set a system property. Follow the instructions at How can I assign more memory to bliss?, except instead of adding a "
-Xmx" property, add
Mac users may have trouble finding the
Library folder. That's because this folder is hidden by default in more recent versions of OS X. There are a number of alternatives to make it visible but if this is just a one-off it may be easiest to use "Go to folder":
~/Library/Preferences/blissand click Go
You should now be able to see the folder in which to store the
In addition to the port above, bliss also opens port 3220, by default, to use internally to check that two instances of bliss have not been started. While it is possible to run multiple instances of bliss on the same server, this is generally advised against without knowing what the repurcussions could be.
The way of customising this port is to use a system property. Again, follow the instructions at How can I assign more memory to bliss?, except instead of adding a "
-Xmx" property, add
-Dbliss.singleinstancemutexsocket=[port of your choice]
The reason this isn't included in the discussion above is that this is only used locally; firewalls don't need to open up this port.
For completeness it's worth mentioning outbound ports. Outbound ports are used where bliss makes a connection to an external service on the Internet, for example looking up cover art.
Outbound ports are short lived and assigned by the operating system and so are generally not controlled in the same static manner as inbound ports. More useful is a knowledge of which external services bliss connects to.
Any other FAQs I forgot or clarifications required? Post your ideas below!