Player axios 0.21.4

belradio123

New Member
Hello. There is the same problem. The Axios player is constantly hanging. IP addresses are different. According to the SP gives out that this is London, United Kingdom. But if you specifically check the IP address, then it gives out that it is google.

IP address: 34.89.97.95


NetRange34.64.0.0 - 34.127.255.255CIDR34.64.0.0 / 10NetNameGOOGL-2NetHandleNET-34-64-0-0-1ParentNET34 (NET-34-0-0-0-0) NetTypeDirect AllocationOriginASOrganizationGoogle LLC (GOOGL-2) RegDate2018 -09-28Updated2018-09-28Refhttps: //rdap.arin.net/registry/ip/34.64.0.0
OrgNameGoogle LLCOrgIdGOOGL-2Address1600 Amphitheater ParkwayCityMountain ViewStateProvCAPostalCode94043CountryUSRegDate2006-09-29Updated2019-11-01Comment *** The IP addresses under this Org-ID are in use by Google Cloud customers. com / legal / go / reportCommentCommentDirect all spam and abuse complaints toCommenthttps: //support.google.com/code/go/gce_abuse_reportCommentCommentFor fastest response, use the relevant forms above.CommentCommentComplaints can also be sent to the GC Abuse deskComment (google-cloud -compliance@google.com) Commentbut may have longer turnaround times.CommentCommentComplaints sent to any other POC will be ignored.Refhttps: //rdap.arin.net/registry/entity/GOOGL-2
OrgAbuseHandleGCABU-ARINOrgAbuseNameGC AbuseOrgAbusePhone+1-650-253-0000OrgAbuseEmailgoogle-cloud-compliance@google.comOrgAbuseRefhttps: //rdap.arin.net/registry/entity/GCABU-ARIN
OrgNOCHandleGCABU-ARINOrgNOCNameGC AbuseOrgNOCPhone+1-650-253-0000OrgNOCEmailgoogle-cloud-compliance@google.comOrgNOCRefhttps: //rdap.arin.net/registry/entity/GCABU-ARIN
OrgTechHandleZG39-ARINOrgTechNameGoogle LLCOrgTechPhone+1-650-253-0000OrgTechEmailarin-contact@google.comOrgTechRefhttps: //rdap.arin.net/registry/entity/ZG39-ARIN

What could it be?
 

Attachments

  • Screenshot 2021-12-28 at 12-02-45 Centova Cast.png
    Screenshot 2021-12-28 at 12-02-45 Centova Cast.png
    44.5 KB · Views: 63

Support

Level 1 Support
Staff member
Hi belradio123,

We believe these are just web crawlers and are of no concern. The user agent is just a piece of data that is supposed to tell a web server some information about the browser that's browsing a web page. The fact that these IPs haven't even gone to the trouble to change the user agent from "axios" to something like "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36" implies a very low level of sophistication of crawling. The user agent field does nothing apart from get saved in a log file and then displayed next to the listener's IP in Centovacast. It's just purely a text field that can sometimes be useful for analytics like telling what's a popular player for your station or website etc.

As our directory lists publicly available radio server pages it's inevitable that web crawlers are going to stumble onto them as all search engines (i.e Google) are using web crawlers to index the web constantly.

I hope this helps to reassure you.
 

belradio123

New Member
Hi belradio123,

We believe these are just web crawlers and are of no concern. The user agent is just a piece of data that is supposed to tell a web server some information about the browser that's browsing a web page. The fact that these IPs haven't even gone to the trouble to change the user agent from "axios" to something like "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36" implies a very low level of sophistication of crawling. The user agent field does nothing apart from get saved in a log file and then displayed next to the listener's IP in Centovacast. It's just purely a text field that can sometimes be useful for analytics like telling what's a popular player for your station or website etc.

As our directory lists publicly available radio server pages it's inevitable that web crawlers are going to stumble onto them as all search engines (i.e Google) are using web crawlers to index the web constantly.

I hope this helps to reassure you.
Thank you for the information
 
Thank you for the information
These so called web crawlers are with two different IP'S in my listeners page for three or more hours,so I don't think they are just listeners...It seems,Geo blocking not working and I can't put Geo block on UK ( one who use that axios) because I am in UK territory.
 

belradio123

New Member
These so called web crawlers are with two different IP'S in my listeners page for three or more hours,so I don't think they are just listeners...It seems,Geo blocking not working and I can't put Geo block on UK ( one who use that axios) because I am in UK territory.
I blocked Player Axios itself and that's it, it disappeared.
 

belradio123

New Member
It's happening right now and terrible..I blocked them in all possible ways.
You need to block exactly Block
User Agent and not IP. If you are using Shoutcast Stream, then in blocks you need to choose to block Block
user agent.
 

Attachments

  • Screenshot 2022-01-21 at 14-26-45 Shoutcast Administrator.png
    Screenshot 2022-01-21 at 14-26-45 Shoutcast Administrator.png
    12.6 KB · Views: 4
  • Screenshot 2022-01-21 at 14-32-00 Shoutcast Administrator.png
    Screenshot 2022-01-21 at 14-32-00 Shoutcast Administrator.png
    13.3 KB · Views: 4
You need to block exactly Block
User Agent and not IP. If you are using Shoutcast Stream, then in blocks you need to choose to block Block
user agent.
I used every possible block option! This is how it looks on Shoutcast stream when I block Axios - it's user agent and IP in gap.
 
Last edited:
Top