Is BeBytes down?
It appears the person kindly donating my server space has gone silent for some time, and hasn’t paid dreamhost their dues, which makes me concerned something has happened. I have brought online my last good snapshot from the local development build on my local server until this is resolved…
7 Likes
the situation has been resolved.
5 Likes
Hi. I assume it’s a known issue, but is this site down?
The link in the first reply works fine here.
It doesn’t here. Is it cached in your browser? Mine reports an invalid DNS.
It works for me, and it’s definitely not cached.
I tried Brave, Chrome and Firefox on my phone. DNS error on all 3. My location is in Wisconsin, USA.
I was wondering if it was a region thing, but I guess not. I’m in Texas, so I reckon it should work. This is a long shot, but maybe try a different DNS? One of the public ones, if you aren’t already.
We’re both talking about the ddns.net Link, right?
I tried it on my phone in the lunch break, and I’m sure I never visited that page on my phone before, so it’s not in the cache.
IP Location Finder - IP Lookup With Detailed Geolocation Data | KeyCDN Tools also confirms the domain exists and is hosted somewhere in West Virginia, USA.
I tried putting the link in your geoLocation page and hostname was not found. I am getting phantom errors while typing this message though. Is there some net bug happening?
Hm,maybe it’s really a problem with your DNS resolver.
I recommnd trying Dismail DNS,they’re very reliable and do even include an Ad/Tracking filter.
https://dismail.de/info.html#dns
I tried fdns2 configuration and it seems to work in everything but BeBytes. I’ll keep that DNS server setting for a while and see what it does.
I tried from multiple machines. multiple DNS options, multiple browsers. Isitdown reports that it’s down.
Also working correctly here ( using google dns )
https://www.be.wildman-productions.org/
This one doesn’t work. Am I supposed to now use this other link?
Yes,the server for the other one is gone,as the first reply in this thread already says.
1 Like
Oh. Same time last year. It was resolved last year, but I’m sure the new billing cycle brought it down.
Can we help with another mirror?