Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by on Tuesday, 29 September 2020 01:17 CDT
There is an update fro my joomla version.
From the joomla update component I'm going to make it start.
After a few seconds a popup appear saying that there is an AJAX loading error: error
On the same server i've no problem in other joomla istances without admin tools, and also no problem in another istance with admin tools but running on apache and not on nginx like this one...
I suppose there is something on the nginx configuration maker or on the application firewall???
Admin Tools does not block Joomla Update. Joomla Update was, in fact, a feature of Admin Tools we donated to the Joomla project a few years ago.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Sorry... probably is a problem with my poor english....
What I'm trying to say is that:
With admin tools and the NGINX configuration generated loaded I have this error....
if I remove from nginx the line that import the configuration generated by admin tools and put the standard code that i previous use with joomla the automatic update works.
(this is what i have now on the nginx config:
gzip on;
gzip_http_version 1.1;
gzip_comp_level 6;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain application/xhtml+xml text/css application/xml application/xml+rss text/javascript application/javascript application/x-javascript
gzip_proxied any;
gzip_disable "MSIE [1-6]\.";
location / {
try_files $uri $uri/ /index.php?$args;
})
So, I think that there is something on the generated nginx config that can break the joomla updater.
I never had any problem updating modules or components, all on the site is working, and I'm really happy to have a tool to increase the security and tune the nginx...
But in this case I think that there is sometingh.... I've also tryied to disable settings in nginx configurator to generate differents cofiguration files... but i cannot found wich setting is causing this problem...
Have you any ideas?? some test to make?? (I've a lot of websites where this is not working and I can check...)
NginX Conf Maker, Allow direct access to these files. Make sure it includes
administrator/components/com_joomlaupdate/restore.php
Nothing else could block the Joomla Update
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
There is. as you can see in attached screenshot
If you cannot reproduce it again with the NginX.conf generated by Admin Tools it might have been a corrupt download or a disruption in your network connection. If you can reproduce it again, the only other possibility I can think of is enabling a long cache time for static resources which could get in the way in some rare cases.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Of course I can reproduce it on all the sites where I've installed it.
I will test and let you know.
If you talk about this settings (see attached), I've tested al the three possibility...
and nothing works...
Now I'm testing removing single lines by hand from your generated nginx.conf.
when I remove this entry it restart to work.
location = /administrator/components/com_joomlaupdate/restore.php {
fastcgi_pass 127.0.0.1:9000;
break;
}
did you think that is this right??
Now removing
administrator/components/com_joomlaupdate/restore.php
from the
Exceptions Allow direct access to these files It works without editing by hand the generated nginx.conf file.
OK, now it makes perfect sense. The problem is your configuration, not the NginX Conf Maker itself.
The line
fastcgi_pass 127.0.0.1:9000;
comes from your configuration of the NginX Conf Maker. Per the documentation, this line is an example and must be changed to match your server configuration. It should a line, or block of lines, used to tell NginX to execute a file as PHP through FastCGI (either direct FastCGI or PHP FastCGI Process Manager a.k.a. PHP-FPM). If you fix that line you will see that not only Joomla Update will work, but the protection features of the NginX Conf Maker will also start working properly :)
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!
