| |
Perff
Administrator
Posts: 1665 |
Server is moved and CSDb is getting new IP
The server CSDb is running on is being moved the night between this thursday and friday, so there might be some downtime around midnight.
They estimate around 45 minutes.
The IP will be changed from 195.41.47.80 to 91.223.235.251, so you know what to put in your hosts-file if you have problems connecting. ;) |
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11129 |
you are doing that to make absolutely sure that even of the certificate was fixed, it's still broken - right? |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1380 |
Hah! The old IP address is already in my /etc/hosts, I guess from last time the site moved.
Hope all goes smoothly, and thanks for keeping the site going :) |
| |
Count Zero
Registered: Jan 2003
Posts: 1825 |
Yeah, fix the cert while at it - even when exp. date is 2031 thats better than expired :) |
| |
Scarzix
Registered: Aug 2010
Posts: 143 |
Why would you need to put a DNS entry in your local hosts file? Isn't CSDb.dk a public domain with an A-record?
Secondly, certificate? Haven't seen one of those on this site as far as I recall, what purpose do we use that for? will we be switching to SSL or? |
| |
Perff
Administrator
Posts: 1665 |
It's not my decision. :)
I just got the message from my hosting company some time ago.
And of cause there is no need to set the hosts file, as I will update the DNS. But I know someone might not want to wait on the DNS to update by itself... ;)
About the cert it's just one of the many todos awaiting my attention. :/
(Help welcome - after Friday. ;) - I know people already sent me links where to get certs, but I probably need a bit more than that. :/ ) |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
Quoting PerffIt's not my decision. :)
About the cert it's just one of the many todos awaiting my attention. :/
(Help welcome - after Friday. ;) - I know people already sent me links where to get certs, but I probably need a bit more than that. :/ )
Here you go: https://certbot.eff.org/ |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: It's not my decision. :)
I just got the message from my hosting company some time ago.
And of cause there is no need to set the hosts file, as I will update the DNS. But I know someone might not want to wait on the DNS to update by itself... ;)
About the cert it's just one of the many todos awaiting my attention. :/
(Help welcome - after Friday. ;) - I know people already sent me links where to get certs, but I probably need a bit more than that. :/ )
I can help you if you like? It's standard Apache or? You do deal with people's passwords so there's really no excuse for not having https. |
| |
Skate
Registered: Jul 2003
Posts: 491 |
I'm not sure if new server configuration can cause a bug like this. Maybe a missing trigger? Please investigate.
Hack Attack 1.1
User Comment
Submitted by Zaadii [PM] on 28 January 2017
I planned this as a update to this version:
HackAttack
but somehow it started it as if it was a new project ?? |
| |
Fredrik
Registered: Apr 2009
Posts: 204 |
This website should get a ssl. So many users and the site has not even got ssl. Shame on you. Lets get professional? |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
ahah, fredrik asking others to get professional, that was funny. |
| |
Digger
Registered: Mar 2005
Posts: 421 |
No but seriously, HTTPS is de facto standard these days. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11129 |
just accept the damn cert then |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
I don't know if self signed certificates will be accepted in future. In chrom(e/ium) based browsers at least you are asked to accept the risk now and then you get in here using https, indicating it's not trusted. |
| |
CreaMD
Registered: Dec 2001
Posts: 3035 |
Let's encrypt is free and works ok. Having valid cert enabled and redirecting to https is only half of the solution. You also need to change all html urls to https:// test everything etc. |
| |
Skate
Registered: Jul 2003
Posts: 491 |
Quote: Let's encrypt is free and works ok. Having valid cert enabled and redirecting to https is only half of the solution. You also need to change all html urls to https:// test everything etc.
I believe better solution is to use // only with URLs. Many CDNs advice to use URLs like this to be able to be both HTTP and HTTPS compatible. I don't know if it has any other side effects but if there is not, please consider changing all http:// URLS to // only instead of https://. This might be useful for the upcoming web standards. Also you can update the URLs in the database before redirecting to SSL and it wouldn't break anything. |
