Fetch timeout validating urls from my domain proximoati.info

[oscarklee]

I have problems using https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/ to validate some urls from my domain proximoati.info.

I have a big amount of urls already validated using my url shortener

but now I'm getting a "Fetch timeout" trying to validate new urls, for example https://www.proximoati.info/gp001

The workaround that I found is use another shortener service to encapsulate my short url:

but I'm unavailable to change all my beacons urls to use the google url shortener service. Seems like my domain is in a blacklist or if I reach some rate limit.

Would really appreciate your thoughts.

[Zimbu98]

Seems to be a problem with your final website, not the shortened URL.

When I entered the shortened URL (https://proximoati.info/gg176) in the validator, I got a "Snap" fail like you did.

But when I tried your ultimate web link (https://proximoati.info/leyde/cafesito/?id=ZWVSM3Z2NCtnZmV1V3ZPeXFCVGQ3QT09), I also got the same "Snap" result.

When I tried your base URL (https://proximoati.info), I got a "Success".

FYI, Google is discontinuing their shortener some time soon, so definitely don't use google for shortening.

[oscarklee]

Thanks for comment,
The weird think is that I can use another shortener service to get success with the failed link.

For example I can shortener the url https://proximoati.info/leyde/cafesito/?id=ZWVSM3Z2NCtnZmV1V3ZPeXFCVGQ3QT09 with bitly.com and get a success with that result in the validator:
https://bit.ly/2q7qNOi

P.d. Thanks for the google info.

[Zimbu98]

I just checked it again and got a Snap even checking your base URL this time. So it is a different result than last time.

I also checked your google shortened version and got a Success as you reported.

Very mysterious!

Random troubleshooting suggestion:

Whenever I check your regular URLs in the validator, it takes a loooong time to get a Snap result back ( I am in the Northwest USA). I am wondering if maybe there is some geographical/distance unhappiness in Google's validator (hence the timeout error)?

When you use the USA-based shorteners, maybe that closer distance makes the validator happier?

Can you try a third-party shortener (i.e. not your own) that is based in Honduras or some other central American country to see if it will work as well as bit.ly and goo.gl?

Another question: You note that these are not validating, but are they appearing in Nearby when you use a beacon to broadcast them and manually scan by opening the Nearby app?

[oscarklee]

I couln't find any shortener service from south america, but I tried with many other services and all worked fine.

moreover, I think the distance is longer when it goes to the bitly services, it's redirected to my own service and then it's redirected again to my final page to fetch the page title, description etc. This vs go to my shortener services and then to my final page.