Experiencing a 401 Unauthorized Error During Update?
If you're seeing a 401 Unauthorized error when trying to update your Joomla extension, it's likely due to our new two-factor authentication (2FA) security measure for your Download ID.
To resolve this, check your email (Spam folder?) for a message to approve your server or device, or read our detailed blog post here(
onlinecommunityhub.nl/best-practice/new-...-extension-downloads) to understand the steps involved. This will guide you through approving your server for future updates.
Need info Full on 500 site down this morning
- Alison Meeks
- Topic Author
- Offline
Less
More
- Posts: 4
- Thank you received: 0
1 week 1 day ago - 1 week 1 day ago #3153
by Alison Meeks
Full on 500 site down this morning was created by Alison Meeks
Working on a dev site and full on front end 500 this morning but admin was accessible. I had just met with the client yesterday to test it... lol because of course!
Anyhow error message is: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /home/klasuser/kuj5.klasusers.com/plugins/system/ochsimplefirewall/src/Helper/IpSetsCache.php on line 210
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /home/klasuser/kuj5.klasusers.com/libraries/vendor/symfony/error-handler/ErrorRenderer/FileLinkFormatter.php on line 1
Very fortunately this isn't on the live site also running Simple Firewall but on J3 - the error is on the J5 dev.
Thanks for your help Ruud and let me know anything else you might require,
Alison
Anyhow error message is: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /home/klasuser/kuj5.klasusers.com/plugins/system/ochsimplefirewall/src/Helper/IpSetsCache.php on line 210
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /home/klasuser/kuj5.klasusers.com/libraries/vendor/symfony/error-handler/ErrorRenderer/FileLinkFormatter.php on line 1
Very fortunately this isn't on the live site also running Simple Firewall but on J3 - the error is on the J5 dev.
Thanks for your help Ruud and let me know anything else you might require,
Alison
Last edit: 1 week 1 day ago by Alison Meeks. Reason: Just formatting - bold had been picked up from error message.
Please Log in to join the conversation.
- Ruud van Lent
- Offline
Less
More
- Posts: 1640
- Thank you received: 107
1 week 1 day ago #3154
by Ruud van Lent
Replied by Ruud van Lent on topic Full on 500 site down this morning
Hi Alison,
So let me first explain what it is doing at the time of the out of memory error:
In ochSimpleFirewall you configure the ipsets that you want to use. Some of these set are small, some are (very) big.
The ipsets are download from the internet and come in a format that we cannot do anything with: we need to convert the ipset to actual ip addresses and store these in a cache file when converted (so the conversion only runs per the cache setting frequency).
Now conversion is taking place in memory, which is limited per php session on your server (which is a good thing). The amount of memory assigned to your session is set via the memory_limit setting in your servers php.ini
Now onto the solution: as you see there are two 'variables' here that we can 'tune' with:
1. deselect the large ipsets (probably stopformspam),
2. increase php memory_limit
Now to make things easier, in ochSimpleFirewall tab Advanced, I have dedicated a setting specifically for this use case:
Set Memory Limit > this can have four values: PHP Configured (default), Low (128MB), Medium (256MN), High (384MB)
so you can configure it here to e.g. high (or medium) and the retry. Note that the setting is only used for generating the ipsets: they do not change the value set on your server php.ini
can you give that a try?
and then a pro tip (especially for the weekend ): updating ipsets can be done via a cron, that way users will never be hit with a slow down etc.
instructions in the plugin advanced settings:
Cache IP sets > Yes, and then read on below this setting.
Hope this helps, if not let me know!
have a nice weekend Alison.
regards,
Ruud.
So let me first explain what it is doing at the time of the out of memory error:
In ochSimpleFirewall you configure the ipsets that you want to use. Some of these set are small, some are (very) big.
The ipsets are download from the internet and come in a format that we cannot do anything with: we need to convert the ipset to actual ip addresses and store these in a cache file when converted (so the conversion only runs per the cache setting frequency).
Now conversion is taking place in memory, which is limited per php session on your server (which is a good thing). The amount of memory assigned to your session is set via the memory_limit setting in your servers php.ini
Now onto the solution: as you see there are two 'variables' here that we can 'tune' with:
1. deselect the large ipsets (probably stopformspam),
2. increase php memory_limit
Now to make things easier, in ochSimpleFirewall tab Advanced, I have dedicated a setting specifically for this use case:
Set Memory Limit > this can have four values: PHP Configured (default), Low (128MB), Medium (256MN), High (384MB)
so you can configure it here to e.g. high (or medium) and the retry. Note that the setting is only used for generating the ipsets: they do not change the value set on your server php.ini
can you give that a try?
and then a pro tip (especially for the weekend ): updating ipsets can be done via a cron, that way users will never be hit with a slow down etc.
instructions in the plugin advanced settings:
Cache IP sets > Yes, and then read on below this setting.
Hope this helps, if not let me know!
have a nice weekend Alison.
regards,
Ruud.
Please Log in to join the conversation.
- Alison Meeks
- Topic Author
- Offline
Less
More
- Posts: 4
- Thank you received: 0
1 week 1 day ago #3155
by Alison Meeks
Replied by Alison Meeks on topic Full on 500 site down this morning
Hey Ruud
Thanks for the detailed explanation. I'll try and work my way through your steps and if I have any hiccups I'll reach out. For now it is turned off so the site is up.
Have a great weekend! Watch out for krampus
Ali
Thanks for the detailed explanation. I'll try and work my way through your steps and if I have any hiccups I'll reach out. For now it is turned off so the site is up.
Have a great weekend! Watch out for krampus
Ali
Please Log in to join the conversation.
- Ruud van Lent
- Offline
Less
More
- Posts: 1640
- Thank you received: 107
1 week 21 hours ago #3157
by Ruud van Lent
Replied by Ruud van Lent on topic Full on 500 site down this morning
Thanks Alison,
I'll keep this topic open for a while: feel free to follow up when needed or when i can close it.
have a great weekend too.
regards,
Rudu
I'll keep this topic open for a while: feel free to follow up when needed or when i can close it.
have a great weekend too.
regards,
Rudu
Please Log in to join the conversation.