Streaming interruption problem
Hi there,
Once again, I would like to thanks the creator of subsonic, this is a wonderful creation and it is highly useful for me. Since the last bug I reported (viewtopic.php?f=5&t=8894), I made a donation and I found another problem. So yeah, I'm here to talk about it.
Since the first time I installed Subsonic on my server, I had always used a SSL connection to my server. On that time, I used the port 442 to listen, stream and watch my stuff on my server. It has always worked and all streams has never fail to me, it was fluid. Recently, I tried something new... and it causes a huge problem when streaming. I hope you guys will be able to help me. Let me explain in details what's going on.
So, as I said, I tried something new on my server. Apache2 already use port 80 and 443 for is own use, so I was unable to use a standard port for subsonic. This problem prevented me to listen my music at my job, because the port 442 is blocked by default. As you guys know, companies often open the standard ports 80 and 443 for browsing purposes, it is necessary, so I decided to look for a solution to my problem without compromising my apache2 server. So I found this subject on your forum : viewtopic.php?t=8525 and I applied what it said to my server. It was a success, the proxy successfully worked. I force a SSL connection through Internet and then, locally, redirect traffic on subsonic on port 442 under the http protocol.
Well now you're wondering what's the problem? Well, there is it: Streaming is damn slow and often never finish to completely load what you're listening. This behavior prevents me to listen music without being interupted. On the top of that, if the stream stops, it forever stops, you need to reclick on the "play" button to have a CHANCE to listen to the complete track without interuption. I tried a lot of things, search a lot for my problem and I never found what could solve this damn thing.
So well, enough explaining what's going on, here's a lot of information that will help us to solve the problem.
1 - First of all, here's the apache2 configuration:
2 - When using Wireshark to catch all packets between my local host and the subsonic server, we can see a shit load of TCP packet errors. I wonder if there's a reason or if this is normal.
3 - At first, when the proxy was configured, I blocked the port 442 from the external network. It certainly force people to use https://music.myhost.ca/ instead of http://myhost.ca:442, but it was to damn unstable. So I opened the port and then the streaming was more bearable. At the same time, I made a second test... I compared the streaming with both addresses, I figured out that streaming directly from the source address (myhost.ca:442) was perfectly fluid.
4 - Downloading my music has the SAME effects. When I start downloading, the first 1.6 - 1.8 MB are downloaded and then BAM, it stops!
5 - I figured out the birate constantly changes by itself when streaming... I wonder why.
If you guys need to do tests on my server, please PM me, I will be pleased to give you credentials and the address.
Thanks a lot!
Dave
Once again, I would like to thanks the creator of subsonic, this is a wonderful creation and it is highly useful for me. Since the last bug I reported (viewtopic.php?f=5&t=8894), I made a donation and I found another problem. So yeah, I'm here to talk about it.
Since the first time I installed Subsonic on my server, I had always used a SSL connection to my server. On that time, I used the port 442 to listen, stream and watch my stuff on my server. It has always worked and all streams has never fail to me, it was fluid. Recently, I tried something new... and it causes a huge problem when streaming. I hope you guys will be able to help me. Let me explain in details what's going on.
So, as I said, I tried something new on my server. Apache2 already use port 80 and 443 for is own use, so I was unable to use a standard port for subsonic. This problem prevented me to listen my music at my job, because the port 442 is blocked by default. As you guys know, companies often open the standard ports 80 and 443 for browsing purposes, it is necessary, so I decided to look for a solution to my problem without compromising my apache2 server. So I found this subject on your forum : viewtopic.php?t=8525 and I applied what it said to my server. It was a success, the proxy successfully worked. I force a SSL connection through Internet and then, locally, redirect traffic on subsonic on port 442 under the http protocol.
Well now you're wondering what's the problem? Well, there is it: Streaming is damn slow and often never finish to completely load what you're listening. This behavior prevents me to listen music without being interupted. On the top of that, if the stream stops, it forever stops, you need to reclick on the "play" button to have a CHANCE to listen to the complete track without interuption. I tried a lot of things, search a lot for my problem and I never found what could solve this damn thing.
So well, enough explaining what's going on, here's a lot of information that will help us to solve the problem.
1 - First of all, here's the apache2 configuration:
- Code: Select all
<VirtualHost *:80>
ServerName music.myhost.ca
ServerAlias music.myhost.ca
ErrorLog /var/log/apache2/subsonic-error.log
CustomLog /var/log/apache2/subsonic-access.log combined
DocumentRoot /var/Server/Apache2/www_null
</VirtualHost>
# music.myhost.ca (ssl)
<VirtualHost *:443>
ServerName music.myhost.ca
DocumentRoot /var/Server/Apache2/www_empty
SSLProxyEngine On
SSLEngine on
SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
# SSLCertificateChainFile /etc/ssl/example.com.cacert.pem
<IfModule mod_proxy.c>
ProxyRequests Off
ProxyPass / http://localhost:442/
ProxyPassReverse / http://localhost:442/
</IfModule>
</VirtualHost>
2 - When using Wireshark to catch all packets between my local host and the subsonic server, we can see a shit load of TCP packet errors. I wonder if there's a reason or if this is normal.
3 - At first, when the proxy was configured, I blocked the port 442 from the external network. It certainly force people to use https://music.myhost.ca/ instead of http://myhost.ca:442, but it was to damn unstable. So I opened the port and then the streaming was more bearable. At the same time, I made a second test... I compared the streaming with both addresses, I figured out that streaming directly from the source address (myhost.ca:442) was perfectly fluid.
4 - Downloading my music has the SAME effects. When I start downloading, the first 1.6 - 1.8 MB are downloaded and then BAM, it stops!
5 - I figured out the birate constantly changes by itself when streaming... I wonder why.
If you guys need to do tests on my server, please PM me, I will be pleased to give you credentials and the address.
Thanks a lot!
Dave