| View previous topic :: View next topic |
| Author |
Message |
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
 Posted: Mon May 28, 2012 7:43 pm Post subject: Icecast inside the www root folder |
 |
|
Ok here is a dilemma since I want to use port 80 but I am currently using Wamp with V-Host what files do i need to put in the root of my wamp www so that I dont have to use the Icecast Apache instead wamp Apache so that I don't have 2 Apaches running all at the same sequence.
See wamp uses port 80 and I also want Icecast to use the same port so my question is, what files do I take from Icecast folders and place in the /root of my current domain www from Icecast? |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu May 31, 2012 1:50 am Post subject: |
|
|
you cannot have 2 applications on the same port at the same time, but you may be able to forward certain requests to icecast through the front end like a reverse proxy.
karl. |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 5:05 am Post subject: |
|
|
Ok I am not sure if were on the same page.
I am asking a very simple question what can I do to remove the apache that comes compiled with Icecast so that I dont have 2 apaches running using up all my CPU at the moment?
Thank You, I will wait for you to answer.
Last edited by Amature DJ on Sun Jun 03, 2012 6:41 am; edited 2 times in total |
|
| Back to top |
|
|
Murrawhip
Joined: 21 Dec 2010
Posts: 58
|
| Posted: Sun Jun 03, 2012 6:37 am Post subject: |
|
|
Once apache binds to a port, you cannot bind icecast to that same port, and vice-versa.
Icecast does not use apache.
As Karl said, you might be able to forward requests through to Icecast's daemon (on a different port). http://lmgtfy.com/?q=apache+reverse+proxy+different+port |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 6:51 am Post subject: |
|
|
| Murrawhip wrote: |
Once apache binds to a port, you cannot bind icecast to that same port, and vice-versa.
Icecast does not use apache.
As Karl said, you might be able to forward requests through to Icecast's daemon (on a different port). http://lmgtfy.com/?q=apache+reverse+proxy+different+port |
Yes Thank you for sharing this but its not giving me the correct answer here.
My domain example (www.9900000hitz.com) points to port 80 just like all other domains that serve off the same server so why cant icecast work the very same way like other domains. How come I cant do this with Icecast?
The answer maybe not that simple, but look if you cant answer my question then don't reply cause im not here to waste your time nor mine.
Thank You
Last edited by Amature DJ on Sun Jun 03, 2012 7:24 am; edited 1 time in total |
|
| Back to top |
|
|
Murrawhip
Joined: 21 Dec 2010
Posts: 58
|
| Posted: Sun Jun 03, 2012 7:24 am Post subject: |
|
|
| Amature DJ wrote: |
My domain example (www.9900000hitz.com) points to port 80 just like all other domains that serve off the same server so why cant icecast work the very same way like other domains. How come I cant do this with Icecast?
|
Domains are websites.
Icecast is not a website.
Mountpoint is to icecast, as website is to apache.
Last edited by Murrawhip on Sun Jun 03, 2012 7:27 am; edited 1 time in total |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 7:27 am Post subject: |
|
|
| Murrawhip wrote: |
Domains are websites.
Icecast is not a website.
Mountpoint is to icecast, as website is to apache. |
Domains and websites are obviously two different things. I am talking about the domain is pointed in the direction of the server and the server hosts the website and why is your Icecast server hosting itself?
Last edited by Amature DJ on Sun Jun 03, 2012 7:29 am; edited 1 time in total |
|
| Back to top |
|
|
Murrawhip
Joined: 21 Dec 2010
Posts: 58
|
| Posted: Sun Jun 03, 2012 7:29 am Post subject: |
|
|
| Amature DJ wrote: |
Domains and Websites are 2 different things. |
I was trying to make things even more simple for you to understand.
Two separate people have told you that only one piece of software can be binded to a port at a time.
Apache is one piece of software, icecast is another.
You cannot attach apache to port 80 while icecast is attached, and vice versa.
If you check the google link I provided, it has the solution that Karl suggested.
This is not an icecast limitation. This is the case with all software that binds to a port. |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 7:33 am Post subject: |
|
|
| Murrawhip wrote: |
| Amature DJ wrote: |
Domains and Websites are 2 different things. |
I was trying to make things even more simple for you to understand.
Two separate people have told you that only one piece of software can be binded to a port at a time.
Apache is one piece of software, icecast is another.
You cannot attach apache to port 80 while icecast is attached, and vice versa.
If you check the google link I provided, it has the solution that Karl suggested.
This is not an icecast limitation. This is the case with all software that binds to a port. |
Again your not understanding my logic. I have a server running websites and the domains are pointed to each one of them off of port 80 and also I have multiple applications/software all running threw port 80 this means that YES Icecast is limiting us if it cant work the same way to host it. |
|
| Back to top |
|
|
Murrawhip
Joined: 21 Dec 2010
Posts: 58
|
| Posted: Sun Jun 03, 2012 7:37 am Post subject: |
|
|
| Amature DJ wrote: |
Again your not understanding my logic. I have a server running websites and the domains are pointed to each one of them off of port 80 and also I have multiple applications/software all running threw port 80 this means that YES Icecast is limiting us if it cant work the same way to host it. |
I'm willing to help you, but if you're only going to tell me I'm wrong when anyone who bothers to google could discover that I'm right, we're not going to get anywhere.
http://stackoverflow.com/questions/1694144/can-two-applications-listen-to-the-same-port
Hosting multiple websites with apache is not the same as binding multiple applications to the same port. Icecast needs a separate port. It's a vital part of TCP/IP.
You're going to need to host Icecast on a separate port, catch traffic on your Apache server that you wish to forward to Icecast, then do so with a reverse proxy. (Link provided earlier)
If you don't understand a particular part of what I'm describing to you, tell me so, instead of simply saying that I'm wrong. |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 7:52 am Post subject: |
|
|
| Murrawhip wrote: |
| Amature DJ wrote: |
Again your not understanding my logic. I have a server running websites and the domains are pointed to each one of them off of port 80 and also I have multiple applications/software all running threw port 80 this means that YES Icecast is limiting us if it cant work the same way to host it. |
I'm willing to help you, but if you're only going to tell me I'm wrong when anyone who bothers to google could discover that I'm right, we're not going to get anywhere.
http://stackoverflow.com/questions/1694144/can-two-applications-listen-to-the-same-port
Hosting multiple websites with apache is not the same as binding multiple applications to the same port. Icecast needs a separate port. It's a vital part of TCP/IP.
You're going to need to host Icecast on a separate port, catch traffic on your Apache server that you wish to forward to Icecast, then do so with a reverse proxy. (Link provided earlier)
If you don't understand a particular part of what I'm describing to you, tell me so, instead of simply saying that I'm wrong. |
I want to make this clear to you that I never said your wrong.
example, I can have all these running at the same time
VHOSTS= (port 80)
Apache listening on mysite.com/www
Apache listening on mysite.com/www1
etc.....
Apache listening on myradiosite.com/www2 ... as for Icecast I cant seem to do this the sameway and this where I am very confused to why it cant be done. 
Thank You |
|
| Back to top |
|
|
Murrawhip
Joined: 21 Dec 2010
Posts: 58
|
| Posted: Sun Jun 03, 2012 7:59 am Post subject: |
|
|
Because, each port can have one application attached to it.
In your case, apache is that application.
You have apache attached to port 80.
Those separate domains you are running from your apache, are still all apart of that one application Apache.
Icecast has its own webserver inbuilt because it doesn't need all the advanced functions of apache, so it's really minimalistic and (in my experience) quick.
For example, on my radio servers, they don't host websites, only Icecast. If I had to install a webserver and get it to cooperate with Icecast, that'd make Icecast much less attractive.
You can have as many websites as you like listening on a port, because the Apache process is handling the incoming requests. If you use a reverse proxy for Apache, Apache could also forward on the appropriate incoming requests to Icecast.
I haven't personally used a reverse proxy, which is why I linked to the google results for using a reverse proxy with Apache. If you do manage to get it working with this method, please let me know, because I might try it myself. |
|
| Back to top |
|
|
Amature DJ
Joined: 17 Apr 2012
Posts: 26
|
| Posted: Sun Jun 03, 2012 8:12 am Post subject: |
|
|
| Murrawhip wrote: |
Because, each port can have one application attached to it.
In your case, apache is that application.
You have apache attached to port 80.
Those separate domains you are running from your apache, are still all apart of that one application Apache.
Icecast has its own webserver inbuilt because it doesn't need all the advanced functions of apache, so it's really minimalistic and (in my experience) quick.
For example, on my radio servers, they don't host websites, only Icecast. If I had to install a webserver and get it to cooperate with Icecast, that'd make Icecast much less attractive.
You can have as many websites as you like listening on a port, because the Apache process is handling the incoming requests. If you use a reverse proxy for Apache, Apache could also forward on the appropriate incoming requests to Icecast.
I haven't personally used a reverse proxy, which is why I linked to the google results for using a reverse proxy with Apache. If you do manage to get it working with this method, please let me know, because I might try it myself. |
Ok I will for sure take a look at this but i hope you realize I have never configured apache to do reverse proxy but im gain to try this and then come back here to post and share with you and others if i manage to successfully do this.
Thank You |
|
| Back to top |
|
|
gerrit
Joined: 25 Apr 2009
Posts: 17
|
| Posted: Mon Jun 04, 2012 5:12 pm Post subject: |
|
|
[quote="Amature DJ"]Ok I am not sure if were on the same page.
I am asking a very simple question what can I do to remove the apache that comes compiled with Icecast so that I dont have 2 apaches running using up all my CPU at the moment?
Icecast does not come with apache why do you think that ? |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
