Recent content by Balanca

Didn't know that phpMyAdmin has 2FA :D

Is it possible to restrict IP access to phpMyAdmin login page? I have external access to phpMyAdmin enabled and I want to make it more secure...

Tnx for the quick answer

Hello, on Plesk I have a domain and mail service us activated for this domain. Users can login directly on webmail.domain.com (Roundcube Webmail). I wonder, is there a way I can customize this login page (for this domain) - add some company info, change background...

Is there any other repo I should use?

Hi, on my Centos7 machine suddenly I'm receiving update error: 022-02-10 13:32:56 INFO: pum is called with arguments: ['--update', '--json', '--', 'MariaDB-client', 'MariaDB-common', 'MariaDB-compat', 'MariaDB-server', 'galera', 'nodejs', 'nodejs-docs', 'nodejs-full-i18n', 'nodejs-libs'...

Hi, I'm getting error message when upgrading: Failed to update Plesk. To solve this problem, you can send the update log to Plesk support. View the update log from Feb 10, 2022. Copy the log to your computer before you close this message. The end of error log looks like this: ... Downloading...

For anyone also having this problem... Service sw-cp-server was not listenig on tcp6. I had to manually create file /etc/sw-cp-server/conf.d/ipv6_ports.inc with following content: listen [::]:8443 ipv6only=on ssl; listen [::]:8880 ipv6only=on; And then restart sw-cp-server service. Upgrade...

I eneded up creating this file and restarting sw-cp-server service. Then plesk upgrade went ok without any warnings. Thanks for helping.

Current version: Plesk Onyx Version 17.5.3 Update #53 I'm trying to upgrade to 17.8.11

Hello IgorG, this file does not exist on my server...

Hello everyone, I can't seem to figure out why sw-cp-server service is not listening for ipv6 on port 8443. This is causing warnings when I try to upgrade Plesk. # netstat -tulpn | grep 443 tcp 0 0 5.189.175.178:443 0.0.0.0:* LISTEN 1734/nginx: master tcp...

Thanks for the answer. So on port 80 are listening ipv4 and ipv6: # netstat -tulpn | grep :80 tcp 0 0 5.189.125.128:80 0.0.0.0:* LISTEN...

I don't understand why port 8880 is open to my ipv4 and not to my ipv6: # ip6tables -S -A INPUT -p tcp -m tcp --dport 8443 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8880 -j ACCEPT

No luck, the same warning was generated in pre-upgrade check :/