audio9 server moving

This morning I am moving the audio9 server to a new data center due to hosting requirements.

If you are using a hard coded IP address for your broadcast client, the new IP address for audio9 will be:

169.44.67.103

Most broadcast clients should automatically connect to the new server. If your feed doesn't automatically connect, reboot your broadcast computer.

Thanks,

Not Working...169.44.67.103

11:26AM (mountain time) Sunday, November 25th 2018

169.44.67.103 = audio9.broadcastify.com (confirmed with my DNS)

NOT WORKING! Your (new?) server NOT accepting my audio stream.

When will it be fixed?

-N0ECT

Lindsay, thank you for the heads-up. The feed I have on Audio9 picked up the new server without issue.

My feed was only down for a few minutes and switched without any problems.

Thanks Lindsay for all you do.

Server Move - Still Broken - Not working

5:54PM (mountain) Sunday, 25NOV2018.

Server move not working.
See attached screen shots.

Reboot, verified DNS and IP address
Revierified my login information and password (see attachments)

NO JOY.

Something changed after the move...I've been a feed provider for YEARS, using same software program to stream my Audio.

Not Happy

Any special firewall our network setup you might have implemented?

Try changing your server port to 8080 or 8000 to see if that resolves the issue.

Connection to Audio9.Broadcastify.com still broken

No Joy!

8:17PM (mountain) Sunday, 25NOV2018

See screen show. No Joy - TCP Port 8080 and 8000 no help, still not working. (see attached)
I have double checked my (connection) password too.
I have been a feed provider for YEARS - with settings as shown.
Something seems to have changed (your end?).
My client just wont connect anymore after move...
Is your (relocated firewall?) accepting inbound connections on Port 80?

Thanks for working on this late Sunday nite...

N0ECT

TAnderson said:

No Joy!

8:17PM (mountain) Sunday, 25NOV2018

See screen show. No Joy - TCP Port 8080 and 8000 no help, still not working. (see attached)
I have double checked my (connection) password too.
I have been a feed provider for YEARS - with settings as shown.
Something seems to have changed (your end?).
My client just wont connect anymore after move...
Is your (relocated firewall?) accepting inbound connections on Port 80?

Thanks for working on this late Sunday nite...

N0ECT

Click to expand...

Why don't you just try substituting 169.44.67.103 for audio9.radioreference.com and then try to reconnect. Nobody else appears to have issues with audio9. I can even connect to audio9, and my feed is not on there. Of course, I will get an error about incorrect password or wrong mount. You aren't even getting connected, which means your software is trying to connect to some IP address that is no longer active.

Mike

Try a traceroute to make sure there isn’t a routing issue somewhere between you and the new data center.

TAnderson said:

No Joy!

8:17PM (mountain) Sunday, 25NOV2018

See screen show. No Joy - TCP Port 8080 and 8000 no help, still not working. (see attached)
I have double checked my (connection) password too.
I have been a feed provider for YEARS - with settings as shown.
Something seems to have changed (your end?).
My client just wont connect anymore after move...
Is your (relocated firewall?) accepting inbound connections on Port 80?

Thanks for working on this late Sunday nite...

N0ECT

Click to expand...

If you would, please give the actual IP address a try as Mike suggested. It's possible that your computer is using a DNS cache with the old Audio9 IP address, which can cause the problems you're experiencing.

Streaming Problem Solved

Streaming Problem Solved (see attached)
The entire Class B subnet your Audio9.Broadcastify.com is on - is registered to South Africa.
I just removed the block on that subnet - at my firewall. Done originally because of too much inbound Spam to my email server.

Everything working now.

Hosting Tip? There is a company that has the domain name @ColoCrossing.com
Absolutely notorious...for providing email hosting systems that Spammers use all the time.
@ColoCrossing.com does not police anything (outbound spam) on the subnets they've been assigned.

73s.
N0ECT

I'm sorry, but you are incorrect. Please don't spread incorrect misleading data.

audio9 is hosted by Softlayer, in Dallas TX.

I realize you've been a feed provider for a long time, but next time something like this happens, please look internally on your own network for problems. 99% of all the feeds recovered within minutes, yet your feed didn't and you blamed us and proclaimed "NOT HAPPY!"

Bad Information?

Disagree,

We DOCUMENTED all our information. Screen shots galore - showing what was not working.
Still a mystery what your (friends?) at Softlayer in Dallas, Texas - are doing using a Class B (IPv4) Subnet - that (I documented again) was assigned (obviously by the InternNic/ARIN) to Western Cape in South Africa.

We do our homework, document, then start asking questions.
Mostly what I see here...are posts (often trying to help) that are 100% opinion - with no associated documentation.

We'll stick with our documentation.
I'd be very careful getting near any IP subnets managed by @ColoCrossing.com
Notorious company for giving "safe harbor" to known Spammers...

73s
N0ECT

TAnderson said:

Disagree,

We DOCUMENTED all our information. Screen shots galore - showing what was not working.
Still a mystery what your (friends?) at Softlayer in Dallas, Texas - are doing using a Class B (IPv4) Subnet - that (I documented again) was assigned (obviously by the InternNic/ARIN) to Western Cape in South Africa.

We do our homework, document, then start asking questions.
Mostly what I see here...are posts (often trying to help) that are 100% opinion - with no associated documentation.

We'll stick with our documentation.
I'd be very careful getting near any IP subnets managed by @ColoCrossing.com
Notorious company for giving "safe harbor" to known Spammers...

73s
N0ECT

Click to expand...

Wrong again. The address space is RIPE IP space leased by SoftLayer. They have many netblocks through RIPE in the vicinity. Not only do many global providers have IP space through multiple RIRs, but in this day and age IPV4 is at a premium and you'll find many companies leasing IP space from providers who have blocks of foreign RIR space. There is absolutely nothing uncommon about this. Enough with the Colocrossing blather.

169.44.0.0-169.44.255.255
169.45.0.0-169.48.255.255
169.50.0.0-169.50.255.255
169.51.0.0-169.51.255.255
169.53.0.0-169.63.255.255

inetnum: 169.44.67.0 - 169.44.67.255
netname: NETBLK-SOFTLAYER-RIPE-CUST-NO1650-RIPE
descr: Hosting Services Inc. (dba Midphase)
country: US
admin-c: NO1650-RIPE
tech-c: NO1650-RIPE
status: LEGACY
mnt-by: MAINT-SOFTLAYER-RIPE
created: 2018-03-30T04:07:04Z
last-modified: 2018-03-30T04:07:04Z
source: RIPE

person: Network Operations
address: 517 W 100 N
address: Suite 225
address: Providence, UT 84332 US
phone: +1.866.398.7638
nic-hdl: NO1650-RIPE
mnt-by: MAINT-SOFTLAYER-RIPE
created: 2018-03-30T04:07:02Z
last-modified: 2018-03-30T04:07:02Z
source: RIPE

PS: Your documentation is pure garbage.

Mike

TAnderson said:

Disagree,

We DOCUMENTED all our information. Screen shots galore - showing what was not working.
Still a mystery what your (friends?) at Softlayer in Dallas, Texas - are doing using a Class B (IPv4) Subnet - that (I documented again) was assigned (obviously by the InternNic/ARIN) to Western Cape in South Africa.

We do our homework, document, then start asking questions.
Mostly what I see here...are posts (often trying to help) that are 100% opinion - with no associated documentation.

We'll stick with our documentation.
I'd be very careful getting near any IP subnets managed by @ColoCrossing.com
Notorious company for giving "safe harbor" to known Spammers...

73s
N0ECT

Click to expand...

Wrong.

The 169.0.0.0 search you did yields a ZA geo location which is correct but only for 169.0.0.0 - 169.0.255.255.

The 169.44.67.103 address is correctly allocated as posted by mtindor, as is the entire range 169.4.0.0 - 169.4.255.255.

Learn how to do a WHOIS properly before beating your chest.
Your issue posted here is entirely a configuration problem on your end