Search results

Well, that sounds quite frustrating if you should come up with some problem while trying to update your site from within Sitejet. Sometimes such bugs just pop up and out of nowhere; someone could be frustrated since, from their end, everything was alright. Have you tried clearing your browser...

To put it simply, it's important to make sure that IPv6 is set up correctly on your server. If your server doesn't support IPv6 or you're not planning to use it, you might want to change the settings for the poppassd service so that it listens on the IPv4 address, which is 127.0.0.1. This is...

Please keep us updated when the fix is gonna be released. A couple of friends of mine also faced the same issue, and I tried to troubleshoot it myself, but nothing worked.

Sorry I couldn't help you here. But it's awesome that you found a solution already. Well, we couldn't dig out in this issue deeper.

It's actually pretty helpful. Just checked it out! Thnx for sharing it!

To start, I'd suggest taking a look at the Mailman logs to see if there are any clues as to why the list stops sending emails after you create a template. These logs are typically found in the /var/log/mailman/ directory. It's a good place to begin troubleshooting.

So, it seems like you're having trouble resetting the stats for how many messages you can send out in Plesk. Here's my suggestion for the first case. Case 1: plesk sbin mailmng-outgoing --destroy This command removes the data.db file, which is why you're seeing errors related to the missing or...

Good for you! I'm just curious: Which solution did you use in the end?

The 'No such file or directory' error usually means that the MySQL socket file is missing or can't be accessed. You might want to check where the socket file is supposed to be in your MariaDB config file (it's often in /etc/my.cnf or /etc/mysql/mariadb.conf.d/50-server.cnf). Just make sure the...

For future references, you can try switching the server Dr.Web uses for updates. Just open its config file (you'll usually find it at /etc/drweb/drweb32.ini or /etc/drweb/drweb_handler.conf) and look for the line that says UpdateServer. Change the website address there to a different one. At...

Based on my own experience with similar issues, I'd suggest checking that there aren't any firewall rules or network settings preventing your computer (NVINCENT-PC) from connecting to the MariaDB server. Sometimes these settings can block communication between your machine and the server, so...

In my experience, it's a good idea to set up your server's firewall to block or limit who can access the ports that the RPC service uses. This is especially important for people trying to connect from outside your network. You can set the firewall to allow only certain IP addresses or groups of...

Alright, so you want to upgrade Node.js from 17.9.1 to 18.17.0 for your React website. Don't worry, even if you're not familiar with Linux coding, it's pretty straightforward with a tool called NVM (Node Version Manager). Here's how I'd do it: Install NVM: First, you need to install NVM. You can...

Oh man, I've been there before. That HTTP 500 error can be a real pain. Here's what I did when I faced something similar on my CentOS 7 server with Plesk 18 (Obsidian): Check Logs: I started by looking at the logs. Plesk keeps its logs in /var/log/plesk/panel.log, and for the web server, it's...

Oh! Wow! That was quick! Thanks for sharing how you did it.

For Yarn to work, you need to have Node.js set up on your server. Once you've got Node.js ready, it's often easier to install Yarn right from the command line, not through the Plesk panel. Just open a command prompt and type npm install --global yarn to install Yarn for the whole system. Also...

I'm afraid it's gonna be the last thing that they gonna do.

It could just be that the update is taking its time. You might just need to wait a bit. But if it's been stuck in maintenance mode for a while, I'd suggest trying to restart your VPS. Sometimes that can fix the issue.

That's actually the simplest way to do it. Why it didn't come to my mind?

Sometimes, this issue can be related to caching settings. Check your server and browser cache settings to ensure they are not causing the 403 errors.