"520" Action: "PUT" /yunohost/api/services/nginx/restart

hi,

My YunoHost server

Hardware: VPS bought online
YunoHost version: YunoHost 11.2.24 (stable)
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen | …
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
I have move my flarum from one yunohost server to another, and also I have upgrade flarum before the migration.

  • changed my nginx config of my website, adding the following
location ~ \.php$ {
    include snippets/fastcgi-php.conf;
    fastcgi_pass unix:/run/php/php8.2-fpm.sock;
}
  • I have check with ‘sudo nginx -t’

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
  • then sudo systemctl reload nginx

I did the following hours ago, but I have restore back to 5 days, to the version where I have selected all the options for system back up. And I was told that I have restore successfully.

So what I did hours ago can be canceled, am I right? If you then you can read directly the Description of my issue part:


Then I upload my assets folder under the public folder, then I was told that The root path /var/www/flarum/public/assets is not readable.

I did the following:

sudo chown -R flarum:flarum /var/www/flarum/public/assets

sudo find /var/www/flarum/public# sudo find /var/www/flarum/public/assets -type f -exec chmod 644 {} \;

I guess I have done something wrong the above command? Because this is what happened. I can run sudo systemctl restart nginx without any seeing warnning.


Description of my issue


Web server is returning an unknown error

Error code 520

Visit cloudflare.com for more information.


By the way, I am using livecan.net, rather than www.livecan.net for flarum site. I even delete this domain on the server. But when I restart ngixn from the webadmin page, it still show that www.livecan.net has 520 error.

the output of sudo less /var/log/nginx/error.log

I can see the similar line every minutes.

2024/08/03 02:32:25 [alert] 1232786#1232786: aborting

And here is the error log: https://paste.yunohost.org/inodokucaj

I am wondering if I should be concerned about anything. I think I should because I cannot restart ngixn from the webadmin page, and also there are constant aborting messages.

By the way, I also got a lot of these Problems:

Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - acpl/my-tags is locked to version 1.4.0 and an update of this package was not requested.
    - acpl/my-tags 1.4.0 requires php ^8.0 -> your php version (7.4.33) does not satisfy that requirement.
  Problem 2
    - brick/math is locked to version 0.12.1 and an update of this package was not requested.
    - brick/math 0.12.1 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
  Problem 3
    - clarkwinkelmann/flarum-ext-mailing is locked to version 1.1.0 and an update of this package was not requested.
    - clarkwinkelmann/flarum-ext-mailing 1.1.0 requires php ^8.0 -> your php version (7.4.33) does not satisfy that requirement.
  Problem 4
    - datlechin/flarum-birthdays is locked to version v2.1.2 and an update of this package was not requested.
    - datlechin/flarum-birthdays v2.1.2 requires php ^8.0 -> your php version (7.4.33) does not satisfy that requirement.
  Problem 5
    - firebase/php-jwt is locked to version v6.10.1 and an update of this package was not requested.
    - firebase/php-jwt v6.10.1 requires php ^8.0 -> your php version (7.4.33) does not satisfy that requirement.

Then I did:

sudo update-alternatives --set php /usr/bin/php8.2
sudo update-alternatives --set phar /usr/bin/phar8.2
sudo update-alternatives --set phar.phar /usr/bin/phar.phar8.2
sudo update-alternatives --set phpize /usr/bin/phpize8.2
sudo update-alternatives --set php-config /usr/bin/php-config8.2

And the composer update went well. I hope I did the right thing.

Any thoughts will be deeply appreciated.

The webadmin basically runs “on top” of nginx. So if you’re restarting nginx from the webadmin, you’re cutting the branch you’re sitting on. Hence the 50x error.

Do you mean that it’s my restart the nginx service, which cause the aborting alert.

But it continues, and I only click the restart button a few times.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.