Centova Technologies Forum
Centova Cast v3 => Bugs and issues => Topic started by: EVS Portugal on December 18, 2016, 05:25:53 am
-
Hello,
WHMSonic has already upgraded shoutcast 1 to Chrome.
Will Centova do the same?
-
Here is some good reading on the matter:
https://bugs.chromium.org/p/chromium/issues/detail?id=669800#c6
and
http://forums.broadcastingworld.com/showthread.php?15313-Google-Chrome-VER-55-is-not-support-shoutcast-V1
-
I had read this information but WHMSonic was able to solve this situation.
I believe that Centova could also resolve
You can read the link below.
http://help.sonicpanel.com/index.php/article/whmsonic-v2218-automated-update-is-released
-
That maybe true, however, the down side is that the new patched version of SHOUTcast version 1 will cause the station NOT to be listed on the SHOUTcast Yellow Pages (YP) listings.
Not sure which one is worse, not working in Chrome, or losing your listing in the YP.
I wonder if WHMSonic realizes this or not.
-
I think they working on it: http://forums.centova.com/index.php?topic=3981.msg12121#msg12121
-
That's just for their web player. It still doesn't address the main Chrome 55 issue.
-
I have been trying to follow the instructions here
http://www.centova.com/en/faq/cast3/information/does_centova_cast_include_a_proxy_for_streaming_on_port_80
however I keep gettting :
Port 80 already appears to be in use on this server:
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 24826/httpd
tcp 0 0 :::80 :::* LISTEN 24826/httpd
If you have already made the necessary changes to avoid a port conflict, you
may force-enable the proxy by running:
/usr/local/centovacast/sbin/setproxy force
Note that if you force-enable the proxy while another application is using port
80, the web interface will fail to start the next time you restart Centova Cast.
I try to forced, I changed the ip like the information suggested and nothing.
-
You must also permit port 80 proxy in account settings under limits
-
I CAN not turn it on in centova cast because I can not even pass the centova cast restart
root@ [~]# /etc/init.d/centovacast restart
Stopping Centova Cast: cc-imaged cc-ftpd cc-web cc-comet cc-appserver cc-control
Starting Centova Cast: cc-control cc-appserver cc-comet cc-web nginx: [emerg] bind() to xxx.xxx.xxx.xxx:80 failed (98: Address already in use)
nginx: [emerg] bind() to xxx.xxx.xxx.xxx:80 failed (98: Address already in use)
nginx: [emerg] bind() to xxx.xxx.xxx.xxx:80 failed (98: Address already in use)
nginx: [emerg] bind() to xxx.xxx.xxx.xxx:80 failed (98: Address already in use)
nginx: [emerg] bind() to xxx.xxx.xxx.xxx:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
- failed
-
Javier looks like you may have another web server installed navigate to http://ip ...
if it is centos and apache run service httpd stop then chkconfig httpd off
-
can you explain that again with a little more details please.
-
ok djduck I were able to understand it now the problem that I have is that in the same server under another ip I have a website and if I run
service httpd stop
chkconfig httpd on
then the website is not loading.
I can see that like that enable the proxy but mess up my site.
-
Try:
service nginx stop
instead of httpd
Then check to make sure all is running.
-
@javier & @scysys - You should post this under a new thread. This has nothing to do with the Chrome / Shoutcast version 1 issue. There have been multiple threads about setting up a proxy server. Search for them, please.
-
Dennis Fallon
this have to be with the google chrome v55 problem
shoutcast v1 are the only one affected and the way to fix it is to create a proxy port 80 / enabling the proxy port 80 or setting up a real dedicated port 80 per account but that will require more that 1 ip address.
if you want to solve your chrome v55 problem
beta testing
Centova Cast v3.2.7.20161212.stable-508r3955 is now available.
Improvements:
Web player for DNASv1 streams now uses proxy (when available) to circumvent new restrictions in Chrome and Safari
-
That won't solve the issue. It only fixed the Player on the one page website. It still won't work in Chrome 55+.
-
read it again...
is telling you what is the solution and that centova will be adjusting the centova cast player to work with the solution because you can not edit the centova cast player yourself. however if you have your own player you can edit the player and use the solution and will work, I just did it and works.
-
Not sure which one is worse, not working in Chrome, or losing your listing in the YP.
not working in Chrome (or any browser for that matter) is going to be far more important than the lack of a YP listing. so many stations are added in other more widely accessible systems (like tunein, itunes radio, etc) that I doubt for most it'd make much difference in not being in the YP.
-dro
-
CentOS 6.4 with centova v3.2.8 already playing in Google Chrome
You can see example in the link below
http://centova.evsradios.eu:2199/start/evsportugal/
All this was done with the help of MyAutoDJ member.
-
yes 3.2.8 start page player is working, but it only works because the account have a proxy, without the proxy 80 will not work.