Stream IP changing

[TRNcommLLC]

Has the IP for audio1.broadcastify.com been changing?
I keep getting notifications that my stream is offline.
I use a Barix Instreamer for my feed and it only accepts an IP.

The IP was 68.169.42.102 but I received an email stating my stream was off line.
I did a DNS lookup and seen the IP was 141.148.32.200 so I changed it but hours later it was down again.
Went back to the old IP and worked for another two or so hours and had to change the IP back again after another email.
Just wondering if this IP 141.148.32.200 is going to be the IP I should be using.

Thanks

 

[SlipNutz15]

Has the IP for audio1.broadcastify.com been changing?
I keep getting notifications that my stream is offline.
I use a Barix Instreamer for my feed and it only accepts an IP.

The IP was 68.169.42.102 but I received an email stating my stream was off line.
I did a DNS lookup and seen the IP was 141.148.32.200 so I changed it but hours later it was down again.
Went back to the old IP and worked for another two or so hours and had to change the IP back again after another email.
Just wondering if this IP 141.148.32.200 is going to be the IP I should be using.

Thanks

Having same issue on 4 of my 6 feeds

 

[GTR8000]

I use a Barix Instreamer for my feed and it only accepts an IP.

I have 6 feeds hosted using Instreamers, and I've never had to enter a BCFY server IP address. The URL works just fine, has for over a decade.

https://support.broadcastify.com/hc/en-us/articles/22099461024539-Barix-Instreamer-Setup-for-Broadcastify

 

[SlipNutz15]

I have 6 feeds hosted using Instreamers, and I've never had to enter a BCFY server IP address. The URL works just fine, has for over a decade.

https://support.broadcastify.com/hc/en-us/articles/22099461024539-Barix-Instreamer-Setup-for-Broadcastify

I had issues back when I originally started using Barix that the DNS name was failing after a internet drop or power blip so I was using IP addresses as well. I'll switch back and see what happens.

 

[GTR8000]

This config has worked flawlessly since 2014. Port 8080 is not necessary, 80 should work just fine, we had some issues with a firewall and it was easier to use 8080 at the time. Never changed is since it ain't broken.

 

[SlipNutz15]

This config has worked flawlessly since 2014. Port 8080 is not necessary, 80 should work just fine, we had some issues with a firewall and it was easier to use 8080 at the time. Never changed is since it ain't broken.

View attachment 202144

Results will vary. I completely understand what you’re saying.

 

[SlipNutz15]

Has the IP for audio1.broadcastify.com been changing?
I keep getting notifications that my stream is offline.
I use a Barix Instreamer for my feed and it only accepts an IP.

The IP was 68.169.42.102 but I received an email stating my stream was off line.
I did a DNS lookup and seen the IP was 141.148.32.200 so I changed it but hours later it was down again.
Went back to the old IP and worked for another two or so hours and had to change the IP back again after another email.
Just wondering if this IP 141.148.32.200 is going to be the IP I should be using.

Thanks

I emailed them and they said they had no server changes or issues but the IP addresses definitely changed.

 

[NVAGVUP]

You are not alone.

Host qty 2 Barix instreamers. Both went off line this morning. IT is unable to successfully verify connectivity to those locations via port 80 or 443.

Per IT, "This seems like a problem on the other end where those devices are rejected our connection / having some sort of other problem?"

 

[GTR8000]

Well I mean, yeah....if you're using static IP's instead of the audio server URL as recommended, it's going to get knocked offline due to the IP change.

 

[blantonl]

Few things here:

1. The IP addresses for your master servers have changed multiple times over the past few months.
2. We’ve emailed each one of you who were still using the old servers that your IP addresses changed (everyone here on this thread was sent an email because we saw your feeds were still connected to the old servers)
3. We had some old servers deprovisioned on 6/1. You didn’t update your devices.
4. Barix devices have supported hostnames now for about 82 years… you just need to update the firmware on your Barix devices

Moral of the story Is….

1. I tried to get ahold of you. We kept a proxy in place so that your feeds wouldn’t go down for an extended time while were thought we were giving you time to migrate. So technically you server IP address didn’t change recently - you were just in a grace period and that expired.
2. Go upgrade your barix devices, or whatever you are using to broadcast, and NEVER EVER EVER hard code an IP address for a server. Ever. Never ever. Never, ever never ever never ever do this. If you hard code an IP address, I will judge you in my sleep, in the morning when I wake up, when I take a poo, and when I take a shower, and my dogs will judge you on their walks.

Right now, infrastructure services across the internet are experiencing rapid velocity of change due to the arms race around AI. We’ve had providers in the span of 6 months close data centers, migrate us to new data centers, and then get out of hosting all together.

Point of note: All our audio infrastructure is now deployed on Papa Larry’s Oracle OCI cloud infrastructure.

 

[blantonl]

This config has worked flawlessly since 2014. Port 8080 is not necessary, 80 should work just fine, we had some issues with a firewall and it was easier to use 8080 at the time. Never changed is since it ain't broken.

View attachment 202144

Port 80 should work, but every single solitary municipal network has hired a firewall administrator that sits in a dark corner of the municipal building running a fiefdom, and he blocks everything outgoing from the city,county,municipal network that is outgoing on Port 80. But of course, exfiltration of audio on 8080, 8000 or 8500 works just fine a lot of the time (LOL)

He also probably blocks Broadcastify too because someone on staff, or some bundled firewall rules filter says we we bad.

You know what, I was recently on site at one of the largest police departments in the world in a conference room to discuss a large project and I’ll be damned if www.broadcastify.com was blocked on the computers there. LOL.

On another note. There is a reason why we have this language on our Barix setup knowledge base article. I swear people will tell me up and down they don’t have a firewall on their Fookysburg Town municipal network but then after 82 days of them trying to setup a Barix device they’ll find the guy sitting in the corner eating Cheetos who indeed was blocking their device with the firewall.

Believe it or not this language below has reduced Barix support requests 8000% (Trump math!)

BEFORE YOU START - READ THIS!!!!

• The Barix Instreamer is primarily used by public safety agencies on corporate / municipal networks that have significant firewall restrictions which prevent outbound internet access from unknown devices on their networks.
• 99.9% of the time, this will affect your configuration of this device on your network, preventing it from connecting to our servers to broadcast your feed, and preventing your feed from coming online.
• We have seen this problem in the vast majority of deployments using the Instreamer in professional corporate / municipal network environments. It is very common with public safety agencies.
• Trust us on this. If your feed doesn't come online after following the instructions below, you have a firewall blocking the device from broadcasting.
• Instead of broadcasting using Port 80 (see the below configuration), try using 8080 or 8000 if your feed does not come online.
• Again, trust us on this. If your feed is not coming online after following the configuration steps below, contact your network engineers or use an alternate port.
• Did we say trust us on this? Because we are hoping that you do. We've dealt with this issue 4 trillion times. Corporate and municipal neworks are wildly restrictive to devices such as these. Your firewall administrator tucked away in the back corner of your network engineering department is waiting for you to come see them.
• Re-read the above and please and thank you.

 

[GTR8000]

Don't even get me started. Imagine having to install a VPN on the PC just to update Notepad++.

 

[VE3PWR]

Has the IP for audio1.broadcastify.com been changing?
I keep getting notifications that my stream is offline.
I use a Barix Instreamer for my feed and it only accepts an IP.

The IP was 68.169.42.102 but I received an email stating my stream was off line.
I did a DNS lookup and seen the IP was 141.148.32.200 so I changed it but hours later it was down again.
Went back to the old IP and worked for another two or so hours and had to change the IP back again after another email.
Just wondering if this IP 141.148.32.200 is going to be the IP I should be using.

Thanks

YES... mine went down yesterday morning too... I made no changes or no changes to router settings or barix settings.
I'm using a Barix instreamer also on Audio9.broadcastify.com using the ip address 68.169.42.100 port 8000 and I can't get it back online after loosing more hair.. lol.. I've change the port to 80 / 8000 / 8080 and still can't get it online.... FUSTRATING...... if i would have received an email with the proper info chanes I would have made the proper changes like in the past...

 

[blantonl]

YES... mine went down yesterday morning too... I made no changes or no changes to router settings or barix settings.
I'm using a Barix instreamer also on Audio9.broadcastify.com using the ip address 68.169.42.100 port 8000 and I can't get it back online after loosing more hair.. lol.. I've change the port to 80 / 8000 / 8080 and still can't get it online.... FUSTRATING...... if i would have received an email with the proper info chanes I would have made the proper changes like in the past...

My brother in Christ did you just read through this thread?

The IP address for audio9 changed long ago from 68.169.42.100

 

[VE3PWR]

My brother in Christ did you just read through this thread?

The IP address for audio9 changed long ago from 68.169.42.100

WOW... yes I did read everything and follow everything .... sorry to upset you.... I thought this is what this fourm is for ? Sorry I'm trying to solve the problem and it's no firewall issue.. sorry to ask

 

[blantonl]

WOW... yes I did read everything and follow everything .... sorry to upset you.... I thought this is what this fourm is for ? Sorry I'm trying to solve the problem and it's no firewall issue.. sorry to ask

Don't worry, I'm not upset. 😏

I think you are misinterpreting my responses here... I'm having fun with a group of power users here. I deal with them every day and you guys will always go off and do things at a level that amaze me and make me shake my head at the same time.

Some of you guys have literal home data centers and implement some of the craziest setups in information and radio technology history, and sometimes you tie yourselves up in Gordian Knots of complexity and it takes hundreds of support requests to untie everything only to hear you say "oh yeah, I DID implement that triple VPN filtering with my own caching DNS server what I wrote myself to solve world peace and to prevent Google from tracking my porn habits and it blocked X from Y and then my firewall got confused because I block by DNS entries so I switched to static IPv6 addresses that go through a triple NAT to IPv4 load balanced over 2 starlink connections and an old ADSL modem. Sorry about that! "

 

[mtindor]

WOW... yes I did read everything and follow everything .... sorry to upset you.... I thought this is what this fourm is for ? Sorry I'm trying to solve the problem and it's no firewall issue.. sorry to ask

If you didn't catch it (and I'm unclear whether you did or not), Lindsay is indicating that you should always use the hostname, not the IP address. Where you have the IP address for audio9, set it to audio9.broadcastify.com instead. That way, if the IP address of audio9.broadastify.com changes (and it will some day, like it has in the past), you won't have to make any changes on your end and things will continue to work.