Search results

Hi John! Have you tried the last 2 steps of the guide? After the statement that says "if the issue persists." That fix should work in cases when it's not possible to find the records to restore. Just make sure you back up the database as instructed in the step 1 of that section.

What he said! ^

Hey! Sorry, I'm a little confused by the wording. You said you don't need webmail, right? If you're asking if it's a requirement to have webmail, then no. You can disable and uninstall it if you prefer. Let me know if you want to know how, or if I understood things wrongly.

Excellent to hear that worked out. Yes, I forgot that some were removed and only had the config files left. I'm glad you sorted it out and everything is working well now. Adding to your last statement; Plesk doesn't carry out the dist-upgrade, the OS does. The Plesk scripts and guides are just...

Thank you, I received the output. Some of the packages on the list are very sensitive. I would still try to remove them, but first I'd create a server snapshot with the hosting provider, so I can easily roll it back in case this takes the server down. Please listen to the warning above. I have...

Either one is okay as long as it lists the deb files. I don't need any other info besides that. Just give me some time for the command, as I have some tasks at work at the moment.

Thank you, then it makes sense that during the dist-upgrade process some packages were left over. Minor glitches during those process can cause such issues. Very well, let me know if you want help with automating that. Otherwise, I look forward to the result.

Yeah, it would take some time. We could write a little scripted command to do it automatically. Are you okay with posting the entire output of repair fs?

Oh my bad, sorry, I'm at work too and missed that one entirely. So these are 2 package from Ubuntu 20.04 and one that was removed but kept the config files. Sounds like none of them should be there. Why don't you try removing them? Should be without dependencies, with a command like this one...

Use process.env.PORT instead. This should allow Passenger to automatically assign the port number: https://support.plesk.com/hc/en-us/articles/12377014316823

Was there only one result of each, or were there multiple lines? Please share the output of the command, if possible.

Hi there, Can you please run this to see if any of these are duplicated? dpkg -l | grep -E "plesk-php82-dba|plesk-milter|sw-librrd" Looking at the version numbers, it looks like the system didn't remove some old packages correctly and the duplicates aren't actually installed, but are still...

Any difference if you use the hostname instead of the IP address on this line? proxy_pass https://192.168.1.30:8443 I see it's private so you may need to add it to hosts, you can figure that out.

How come you can't edit the custom ones? are they greyed out or what does it look like?

Have you tried removing this and testing without it?

Please confirm whether it works when you use the port or not

Thanks for sharing, glad to hear you sorted it out.

Yes, that's fine. When the issue happens again, open that file with atop as shown in the guide I linked, and go to the timestamp when the problem happened.

Yes, you're supposed to use {WEBSPACEROOT}. It has this value by default, so just set it to default to see what it should look like. I'm not sure if I understood correctly, but if you're manually importing sites one-by-one then you can edit their PHP settings too, no? In any case, if you can't...

Thanks for confirming that it's working again. It was actually not any change in behavior or something particular to your old version. We just had an issue in the past few days, but it's been resolved already: https://support.plesk.com/hc/en-us/articles/31409804928791