ThinkServer:News: Difference between revisions
m Corrected errors |
m →New Developments!: Word correction |
||
| Line 7: | Line 7: | ||
== New Developments! == | == New Developments! == | ||
We have managed to acquire and enabled a domain | We have managed to acquire and enabled a domain name to the server. This is [https://freddythechick.uk freddythechick.uk]. This has allowed us to set and use more services than before. We have set up IPSec-IKEv2 connection for VPN connections to our mobile phones. We have managed to put the website to be internet facing and have enabled TLS with Let's Encrypt so it is now trusted by all browsers, it is also persistently encrypted and we have disabled unused old ciphers, only allowing AES-GCM with modern browsers. We are currently using ECDHE-RSA for key negotiation but will use ECDHE-ECDSA as soon as Let's Encrypt support it (support is coming soon). We have set up a local DNS server to redirect requests to our domain name locally to the server instead of through the Internet. | ||
Next to be sorted is possibly and e-mail server at some point - watch this space! | Next to be sorted is possibly and e-mail server at some point - watch this space! | ||
Revision as of 01:26, 19 May 2017
Asterisk now running on Xen
We have moved the Asterisk virtual machine from a KVM/QEMU machine to a Xen Hypervisor. Xen is a bit closer to the metal and is now included as standard in the standard Kernel modules. We wanted to use Xen originally but the separate kernel had problems. Now it is integrated, it is a lot easier to set up and get going, with no negligible impact.
--Sam (talk) 02:53, 30 March 2017 (UTC)
New Developments!
We have managed to acquire and enabled a domain name to the server. This is freddythechick.uk. This has allowed us to set and use more services than before. We have set up IPSec-IKEv2 connection for VPN connections to our mobile phones. We have managed to put the website to be internet facing and have enabled TLS with Let's Encrypt so it is now trusted by all browsers, it is also persistently encrypted and we have disabled unused old ciphers, only allowing AES-GCM with modern browsers. We are currently using ECDHE-RSA for key negotiation but will use ECDHE-ECDSA as soon as Let's Encrypt support it (support is coming soon). We have set up a local DNS server to redirect requests to our domain name locally to the server instead of through the Internet.
Next to be sorted is possibly and e-mail server at some point - watch this space!
--Sam (talk) 03:20, 7 June 2016 (UTC)
PHP 7 Support
PHP has been updated to PHP 7, which is supposed to have a large speed boost over previous versions. We are pushing this version and keeping an eye out for any issues as this is the first major PHP release in many years. So far everything seems to be OK as before.
--Sam (talk) 22:43, 6 May 2016 (UTC)
HTTP/2 Support
We have enabled HTTP/2 support on the server when used with https. We only have a self signed certificate at the moment so an exception needs to be created, but after that, you should notice that the site is now overall faster than before. You will need a modern browser to take advantage, however with an older browser, the site should still work.
--Sam (talk) 20:12, 11 April 2016 (UTC)
EDIT: We are no longer using self signed certificates, our certificate is signed by LetsEncrypt and should not throw up an error (unless there is actually a problem) anymore.
--Sam (talk) 04:47, 30 November 2016 (UTC)
Welcome back all!
Due to a hardware failure, the server has been down for over a month. The CPU and motherboard had failed. After contacting IBM and getting it fixed under warranty, the server is now back up and running! No data was lost as a result. The new CPU has been reseated with more heat sink paste than the original, this was the suspected cause of the first failure. All seems to be running fine now. Thanks for your patience.