karlheyes / icecast-kh

KH branch of icecast
GNU General Public License v2.0
300 stars 107 forks source link

can't conect to stream on last github master #408

Closed edinsof closed 1 year ago

edinsof commented 1 year ago

Hi after update to master github version y get a error on any centovacast station

i cant connect to stream and icecast page status is downloading a xsl file centovacast

Vyacheslav-S commented 1 year ago

I also have such a problem when the server is running for several hours or days. I solve this problem by restarting the icecast service: sudo systemctl restart icecast

karlheyes commented 1 year ago

can you check with the master tree, see if you get the right response now?

karl.

edinsof commented 1 year ago

Solved with last master tree

edinsof commented 1 year ago

xmlfile log.txt

i updated to last master and error back- also sc_trans can't connect

karlheyes commented 1 year ago

can you clarify what request you are getting there on the web page, and what headers you get. Assuming it's /stream.xspf then curl -v http://host:8000/stream.xspf if it is and admin request then curl -v http://admin:pw@.../admin/...xsl You can blot out any confidential info, I just looking at what is sent received and what the error log is reporting.

karl.

karlheyes commented 1 year ago

the metadata update failure is not useful. Any further details on what the body of the response says? or the error log reports, even the length of the 400 response in the access log might help

I'm assuming the 400 response is because the stream disconnects, so there is no stream to update. Do you know the cause for that disconnection?

karl

edinsof commented 1 year ago

error.log this error log stream start but autodj dont connect

edinsof commented 1 year ago

access.log and this es acceslog

karlheyes commented 1 year ago

what do you have set up for the ports and shoutcast settings in the xml?

edinsof commented 1 year ago

server.txt

this works fine on ( Icecast 2.4.0-kh15)

karlheyes commented 1 year ago

I thought I had fixed the older style layout previously when doing the xml parsing changes but it looks like that got by and the mountpoint was unset forcing the drop on the connection attempt. I've reworked that and pushed to the master tree so you can verify.

karl.

edinsof commented 1 year ago

seems to have been fixed.

I'll try it in the other streams and I'll let you know

karlheyes commented 1 year ago

thanks, also let me know if the other aspect is occurring and if it does, what you are seeing in the error log and the headers from the request (eg curl -v)