Webserver changes summer 2020 - Revision history

Bert at 10:32, 21 December 2020

2020-12-21T10:32:03Z

← Older revision		Revision as of 12:32, 21 December 2020
Line 28:		Line 28:
	=== Client IP address ===		=== Client IP address ===
	Currently, the [[Getting Apache logs\|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software\|ULYSSIS security measures]].		Currently, the [[Getting Apache logs\|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software\|ULYSSIS security measures]].

			[[Category:Webserver]]

Bert: /* Support for php_flag and php_value */

2020-07-20T03:15:17Z

Support for php_flag and php_value

← Older revision		Revision as of 05:15, 20 July 2020
Line 20:		Line 20:

	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
	{{info\|~~Want~~ to ~~make sure you haven't missed any~~ php_flag or php_value ~~in your .htaccess files? You can find an easy tool to check~~ [https://docs.ulyssis.org/summer2020tool/ ~~here~~]}}		{{info\|To help users trying to find out if their accounts still contain problematic cases of php_flag and php_value, we've introduced a [https://docs.ulyssis.org/summer2020tool/ simple tool] that tries to automatically check all .htaccess files that are in use.}}
	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

Bert: /* Support for php_flag and php_value */

2020-07-19T20:49:51Z

Support for php_flag and php_value

← Older revision		Revision as of 22:49, 19 July 2020
Line 21:		Line 21:
	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
	{{info\|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [https://docs.ulyssis.org/summer2020tool/ here]}}		{{info\|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [https://docs.ulyssis.org/summer2020tool/ here]}}

	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

Bert: /* Support for php_flag and php_value */

2020-07-19T20:49:41Z

Support for php_flag and php_value

← Older revision		Revision as of 22:49, 19 July 2020
Line 20:		Line 20:

	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
	{{info\|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [[https://docs.ulyssis.org/summer2020tool/\|here]]}}		{{info\|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [https://docs.ulyssis.org/summer2020tool/ here]}}

	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

Bert: /* Support for php_flag and php_value */

2020-07-19T20:49:18Z

Support for php_flag and php_value

← Older revision		Revision as of 22:49, 19 July 2020
Line 20:		Line 20:

	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
			{{info\|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [[https://docs.ulyssis.org/summer2020tool/\|here]]}}

	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

Vincenttc at 09:59, 9 July 2020

2020-07-09T09:59:51Z

← Older revision		Revision as of 11:59, 9 July 2020
Line 8:		Line 8:
	== What will change? ==		== What will change? ==

	We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, ~~one~~ can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal".		We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal".

	* PHP will be updated from 7.2 to 7.4		* PHP will be updated from 7.2 to 7.4
Line 20:		Line 20:

	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how ~~one~~ can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

	=== Basic Auth in PHP and FCGI scripts ===		=== Basic Auth in PHP and FCGI scripts ===

Bert: /* Client IP address */

2020-07-08T23:37:58Z

Client IP address

← Older revision		Revision as of 01:37, 9 July 2020
Line 26:		Line 26:

	=== Client IP address ===		=== Client IP address ===
	Currently, the [[Getting Apache logs\|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP ~~adres~~ will be the ~~clients~~ IP ~~adres~~, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for ~~Wordpress~~ installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software\|ULYSSIS security measures]].		Currently, the [[Getting Apache logs\|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software\|ULYSSIS security measures]].

Bert: /* Support for php_flag and php_value */

2020-07-08T23:36:08Z

Support for php_flag and php_value

← Older revision		Revision as of 01:36, 9 July 2020
Line 20:		Line 20:

	=== Support for <code>php_flag</code> and <code>php_value</code> ===		=== Support for <code>php_flag</code> and <code>php_value</code> ===
	Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if ~~the~~ the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.		Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714\|Managing PHP errors]] and [[Special:PermanentLink/715\|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs.

	=== Basic Auth in PHP and FCGI scripts ===		=== Basic Auth in PHP and FCGI scripts ===

Bert: /* When are the changes planned? */

2020-07-08T23:01:15Z

When are the changes planned?

← Older revision		Revision as of 01:01, 9 July 2020
Line 4:		Line 4:
	== When are the changes planned? ==		== When are the changes planned? ==

	The ~~change~~ will be in effect after the downtime in ~~september~~ when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration.		The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration.

	== What will change? ==		== What will change? ==

Bert at 23:00, 8 July 2020

2020-07-08T23:00:22Z

← Older revision		Revision as of 01:00, 9 July 2020
Line 1:		Line 1:
	This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these		This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these
	instructions are not clear to you, or if you have some more questions about the ~~change~~, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''.		instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''.

	== When are the changes planned? ==		== When are the changes planned? ==