| 14 Jul 2025 |
 @n4ch723hr3r:nope.chat | or maximum IPs | 14:36:47 |
| @n4ch723hr3r:nope.chat | if you cant you would just have to code up something yourself xD | 14:37:01 |
| @n4ch723hr3r:nope.chat | thats how i would do it at least :3 | 14:37:14 |
 Zhaofeng Li | Hmm wait, so the http stream used by the listener can be proxied right? Is it just the source that's problematic? | 14:38:02 |
| @n4ch723hr3r:nope.chat | the problem with icecast is that, for whatever reason, it uses the same port for http as it does for raw TCP streams | 14:38:46 |
 matthewcroughan | It's the fact that icecast wants to do what nginx is doing yes | 14:39:03 |
| matthewcroughan | putting an nginx in front of icecast who wants to be in control of all this stuff, makes it a PITA | 14:39:27 |
| matthewcroughan | I don't doubt it can be done, I just don't know how, and it seems like a waste of time | 14:39:44 |
| Zhaofeng Li | In reply to @n4ch723hr3r:nope.chat
the problem with icecast is that, for whatever reason, it uses the same port for http as it does for raw TCP streams Can the listener use the nginx-proxied endpoint, while the streamer accesses icecast directly over wireguard or whatever | 14:40:33 |
