2017-01-28 lost posts
2017-01-28 lost posts
Today, we seem to have lost a lot of posts (there where less than usual).
PLASMA's posts also got lost (new thread) informing, that he's using a new Hoster.
This may be due to a necessary switching of DNS servers, and IP addresses.
PLASMA's posts also got lost (new thread) informing, that he's using a new Hoster.
This may be due to a necessary switching of DNS servers, and IP addresses.
Re: 2017-01-28 lost posts
It's worse for me!
When I try to connect to freebasic.net from my professional PC, I get now a page (freebasic.net/cgi-sys/suspendedpage.cgi) with only a big message:
ACCOUNT SUSPENDED
This Account has been suspended.
Contact your hosting provider for more information.
When I try to connect to freebasic.net from my professional PC, I get now a page (freebasic.net/cgi-sys/suspendedpage.cgi) with only a big message:
ACCOUNT SUSPENDED
This Account has been suspended.
Contact your hosting provider for more information.
Re: 2017-01-28 lost posts
It get's worse WIKI wrote:
Error: Unable to connect to the database.
Error: Unable to connect to the database.
Re: 2017-01-28 lost posts
Yes, I had to move hosts. Hopefully will be the last time for a long time.
If you are seeing "account suspended", your cached or ISP DNS is still pointing to the old sever. You can set your hostfile to use 198.252.109.13 for freebasic.net or temporarily use 4.2.2.1/4.2.2.2 for your DNS servers.
The wiki should be fixed now.
If you are seeing "account suspended", your cached or ISP DNS is still pointing to the old sever. You can set your hostfile to use 198.252.109.13 for freebasic.net or temporarily use 4.2.2.1/4.2.2.2 for your DNS servers.
The wiki should be fixed now.
Re: 2017-01-28 lost posts
That came back but my today update is lost!MrSwiss wrote:It get's worse WIKI wrote:
Error: Unable to connect to the database.
[edit]
I updated Wiki again now.
Last edited by fxm on Jan 29, 2017 9:39, edited 3 times in total.
Re: 2017-01-28 lost posts
I have none rights on my professional PC.Plasma wrote:If you are seeing "account suspended", your cached or ISP DNS is still pointing to the old sever. You can set your hostfile to use 198.252.109.13 for freebasic.net or temporarily use 4.2.2.1/4.2.2.2 for your DNS servers.
Re: 2017-01-28 lost posts
If you are using a router you can set the DNS in there. You can also try running "ipconfig /flushdns" and restarting. Otherwise you will just have to wait for the changes to propagate.
Re: 2017-01-28 lost posts
Always "account suspended" with my professional laptop when trying to access freebasic.net.
On my professional laptop, internet access is redirected from the site of my company (the only one where I can connect), so I can only wait and pray.
On my professional laptop, internet access is redirected from the site of my company (the only one where I can connect), so I can only wait and pray.
Re: 2017-01-28 lost posts
My prayer was effective!
Everything now comes back well on my professional laptop.
The only problem that remains is the loss of some posts yesterday on forum (less than a dozen I think).
Everything now comes back well on my professional laptop.
The only problem that remains is the loss of some posts yesterday on forum (less than a dozen I think).
Re: 2017-01-28 lost posts
On my end, the DNS (already 24hours ago) resolved the new IP correctly for:fxm wrote:My prayer was effective!
Everything now comes back well on my professional laptop.
freebasic.net
but e.g.:
www.freebasic.net
*still* points to the old IP (and there's a whole lot of links, which use the www.-prefix).
Not sure if that is still a problem of "changes in the DNS, trickling through too slowly"
or whether www.freebasic.net needs to get an explicit nudge into the right direction
on the side of the provider.
I currently have to manually edit the www.-subdomain-prefix away, in many places
which contain the www.-prefixes in their Link-URLs...
Olaf
Re: 2017-01-28 lost posts
works ok for me, I live in Texas
Re: 2017-01-28 lost posts
If you can get to freebasic.net, then it's likely a caching problem somewhere on your end. I would try another computer or browser.OSchmidt wrote:On my end, the DNS (already 24hours ago) resolved the new IP correctly for:fxm wrote:My prayer was effective!
Everything now comes back well on my professional laptop.
freebasic.net
but e.g.:
http://www.freebasic.net
*still* points to the old IP (and there's a whole lot of links, which use the http://www.-prefix).
Not sure if that is still a problem of "changes in the DNS, trickling through too slowly"
or whether http://www.freebasic.net needs to get an explicit nudge into the right direction
on the side of the provider.
I currently have to manually edit the http://www.-subdomain-prefix away, in many places
which contain the http://www.-prefixes in their Link-URLs...
Olaf
Re: 2017-01-28 lost posts
It works for me now too since a few hours, but it took quite long for the change to propagate.
Maybe some additional local caching is causing trouble? For example Windows and Firefox both do cache DNS responses.
Maybe some additional local caching is causing trouble? For example Windows and Firefox both do cache DNS responses.
Re: 2017-01-28 lost posts
Since a few hours, now also the www-prefixed domain does resolve correctly for me.St_W wrote:It works for me now too since a few hours, but it took quite long for the change to propagate.
Maybe some additional local caching is causing trouble? For example Windows and Firefox both do cache DNS responses.
Olaf