«Oops, something went wrong» after upgrade to v0.10.6

[stemy2]

Hello,

I can't use pixelfed anymore since the last update. After logging on, i have the message «Oops, something went wrong». I tried the solution mentioned there, but it solved nothing.

[yalh76]

Sorry, without logs, we can't help you.

[lapineige]

@stemy2 did the upgrade worked correctly ? (no error message)

[lapineige]

I upgraded again to the same version (from v0.10.6), and now I have this error…

connect() to unix:/var/run/php/php7.3-fpm-pixelfed.sock failed (2: No such file or directory) while connecting to upstream, client: 136.243.88.169, server: domain.tld, request: "POST /users/Pseudo/inbox HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.3-fpm-pixelfed.sock:", host: "domain.tld" FastCGI sent in stderr: "PHP message: PHP Warning: require(/var/www/pixelfed/vendor/composer/../spatie/laravel-backup/src/Helpers/functions.php): failed to open stream: No such file or directory in /var/www/pixelfed/vendor/composer/autoload_real.php on line 66 PHP message: PHP Fatal error: require(): Failed opening required '/var/www/pixelfed/vendor/composer/../spatie/laravel-backup/src/Helpers/functions.php' (include_path='.:/usr/share/php') in /var/www/pixelfed/vendor/composer/autoload_real.php on line 66" while reading response header from upstream, client: 116.203.17.124, server: domain.tld, request: "GET /api/v1/instance HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.3-fpm-pixelfed.sock:", host: "domain.tld"

And autoload_real.php does exit… (with no line 66…) Same for /var/www/pixelfed/vendor/spatie/laravel-backup/src/Helpers/functions.php

[lapineige]

Note: everything works except the main timeline.

[lapineige]

@yalh76 can you reopen this issue ? Thanks :)

[lesamarien]

log-install-pixelfed.txt

Hello

I just installed Pixelfed 0.10.6 on my Yunohost 3.6.5.3. The installation went well. I created my account and put in admin. When I connect, I have the same problem, I have the following message:

"Oops, something went wrong Please reload the page. "

I manage to post photos but in the home page, there is a circle constantly rotates and does not display the photos.

I enclose the installation log if it can help you.

Thank you for your help

[lapineige]

Restarting php7.3-fpm did work… it's strange, I'm sure that one of the first things I tried. Solved for me

[ghost]

@lapineige, greate to hear that you found a solution. Running service php7.3-fpm restart didn't solve the problem for me.

Any other ideas?

My szenario is similar to @lesamarien (new installation)

[lapineige]

And mine was only an upgrade (from the same version ^^).

Can you check php logs ? (after going to Pixelfed, to the page where you have this issue)

[ghost]

sadly there is nothing in the logs (via GUI php7.3-fpm)

[lapineige]

No error or warning at all after encountering the issue ?

I have the issue again… And also any post with a # is not well federated, has no title displayed in my Pixelfed (but it's fine from somewhere else, including Mastodon)

[lesamarien]

Hello

After updating Yunohost, an update of PHP7.3 has been made and Pixelfed is working again.

[lapineige]

For me, it seems to be the contrary: it fails since the last update.

[lapineige]

I don't find any relevant log… When I have this issue, the log says:

[pool pixelfed] child 17839, script '/var/www/pixelfed/public/index.php' (request: "POST /index.php?/api/pixelfed/v1/media") executing too slow (5.790417 sec), logging [pool pixelfed] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 6 total children [pool pixelfed] server reached pm.max_children setting (10), consider raising it

edit: in fact, it seems to be older log. I changed pm.max_children to 25, no change in Pixelfed.

After reloading the main page, still the same error :(. Nothing in the logs.

[lapineige]

I tried to "upgrade" again to the same version, still the same issue… @yalh76 have you any idea about how I can provide more logs or debug this ?

[ghost]

After an update today the error was gone but came back to life when I opened the registration and let one person run a registration. (still nothing in the logs) maybe this is helpful

[lapineige]

Fixed by #91 edit: I mean fixed by the upgrade, maybe not by the PR itself I hope it will last this time… 😄

[yalh76]

Fixed by #91 I hope it will last this time… 😄

Thanks a lot, I will check that PR

[lapineige]

I have this issue again… 😞 I think I've found what's the problem : it happens (at least for now, I don't know for the past issues) only if I add alternative text to my image.

[yalh76]

I have this issue again… 😞 I think I've found what's the problem : it happens (at least for now, I don't know for the past issues) only if I add alternative text to my image.

And do you know if it's YunoHost specific ?

[lapineige]

No, and I don't see a way to make sure it is (not) related to Yunohost. I did not find any related issue on pixelfed repo.

[yalh76]

Maybe you should ask at the upstream app ;p

[stemy2]

For me, the problem is solved.