You are here: Home » Reply

Reply To: FirePlay Flash client for FireFly



Hello music fans.

I’ve got the same problem as some of you reported – at work, the firewall is blocking everything except port 80 and 443.
So I needed a workaround to get fireplay working on port 80 (or 443).
Here is how I managed it to work with IIS6.

You may need an own domain or dynamic DNS accout which you can manage. In my scenario I setted up a new subdomain cos the main (www.) domain is already pointing to the WHS home page.
I got my router configured to update my account regulary. In my domain administration I created a CNAME record for so it is always reachable by that name. The same I did for the new subdomain: pointing to a CNAME record that is my address.
BTW it’s easy to get this domain even used by the MSS’s Webshare by editing just a few entries in the registry.

Enough of off topic talk, lets go to work:

1a. we need a .NET URL Rewriter and Reverse Proxy. Read more about it at and download the latest build there.

1b. create a new folder in i.e. C:Inetpub called “music”

1c. inside this folder create a new text file, name it “ManagedFusion.Rewriter.rules” and put in the following text:

RewriteEngine On
RewriteRule ^(.*)$ http://localhost:9999$1 [P]

1d. now extract from the downloaded “Managed Fusion URL Rewriter” the file called “web.config” to your new dir (C:Inetpubmusic)

1e. in “C:Inetpubmusic” create a folder called “bin” – to this folder extract the “ManagedFusion.Rewriter.dll”

After these steps your folder structure should look like this:

C:Inetpubmusic – containing “web.config” and “ManagedFusion.Rewriter.rules”
C:Inetpubmusicbin – containing “ManagedFusion.Rewriter.dll”

Now we need to create a new website in IIS.

2a. create a new website listening on port 80, homedir is the folder you created in 1b. Name it whatever you like.

2b. edit properties for this new website. On “Website” tab select advanced settings for the “IP Address” binding. Add there a new Hostheader entry to which this website will listen on, i.e. – don’t forget to create this subdomain in your domain administration of your provider. A dyndns address should work fine too.

2c. this website does not need any rights to run scripts or list directory content! Edit properties, go to Home Directory tab and disable everything!

2d. in the same tab, under application settings click on “Configuration”. Add a new “Wildcard application map” pointing to “C:WINDOWSMicrosoft.NETFrameworkv2.0.50727aspnet_isapi.dll” and UNCHECK “verify that file exists”!

That’s all. You don’t need to change anything on firefly or fireplay.
Now you should be able to reach fireplay website going to – keeping in mind, that your calling it by it’s new, dedicated (sub)domain!
If you miss “fireplay.html” at the end you will get the firefly admin-page. To change that, you will need to rename your fireplay.html file to index.html. Rename the existing (original) index.html to admin.html or just move it out there.