Search results

Any news on mailman 3 support?

@IgorG Please help?

Please check again. It must be a different account, since root is able to ssh without issues. Maybe chrooted?

Error message on once again confirmation of ssh-storage: Error: Failed to create the directory "/../../../storage" at sftpstorage.foo.bar: unable to make SSH connection: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain And yes...

Additionally clicking "Backup" in Tools&Settings now takes forever to load. Once it loads, screen fills with yellow warnings

It is the sftp storage for backup. The only thing that changed is the host key of the target server, which hosts the sftp storage. But: all that is automatic. So my assumption is: there is a known_hosts file, which has the old server key.Which account, where is the file? So I can delete the...

@IgorG maybe you have an idea? Is there a "known_hosts" for the sftp backup storage? If so, how to modify it? OR what can it be?

Yes I can. Keep in mind, it is pubkey exchange. And all that changed is the remote sftp-Storage-server, so a new host-key. Everything else is the same.

Plesk Obsidian Version 18.0.51.1 OS Red Hat Enterprise Linux release 8.7 (Ootpa) Extension SFTP backup Storage Extension Since the switch to a new backup-Server the sftp-backup no longer works: Transport error: Extension transport: ext://sftp-backup/server/: Failed to list the directory "" at...

Username: TITLE plesk installer update - ERROR PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.50.2, Red Hat Enterprise Linux release 8.7 (Ootpa), x86-64 PROBLEM DESCRIPTION Issuing a plesk installer update results in error messages during update: PHP...

Username: TITLE plesk repair installation - breaks phpmyadmin installation PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.50.2, Red Hat Enterprise Linux release 8.7 (Ootpa), x86-64 PROBLEM DESCRIPTION The command plesk repair installation breaks the...

Its most likely related. While I can assign certificates in the backend. Problem is simply as outlined above: the wildcard domain is not in the vhost files and therefore the server doesnt assign the correct domain. Well only sometimes if by chance the right vhost is assigned to the request.

Reinit solved the issue - yikes. *solved*

User name: Martin_Sauer TITLE ICMP rule in firewall management "lost" PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS 7.5, Obsidian 18.0.26, web host edition PROBLEM DESCRIPTION There is no ICMP rule in Plesk Firewall under Tools&Settings. As a result ICMP is denied by...

User name: Martin_Sauer TITLE wildcard subdomain PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS 7.5, Obsidian 18.0.26, web host edition, apache + nginx (in default config without custom folder according last update) PROBLEM DESCRIPTION The behaviour as outlined in...

@IgorG any idea? Or do you consider it a bug?

Ok so I dont see any nginx directive, where a server listens Ok we got a similar config. @IgorG we got a problem here. Seems we found a bug - can you take a look? Configured *.example.com subdomain according documentation. Yesterday I know for sure the wildcard worked for frontend, but...

Its getting weird. Seems we found a bug. Just yesterday I secured a domain with a wildcard domain and had it all work. Now the nginx "randomizer" kicks in, in default config. So when connecting to a non-existant domain, the nginx server doesnt catch the wildcard, but instead a random other...

The ACME challenge is only to issue the certificate. Did you check the certificate on Example Domain ? Reviewing the certificate should show "*.example.com" and "example.com". Like in the article: create the subdomain "*.example.com" but pointing to the homedir of "example.com". You should have...

I assumed you do have a current wildcard ssl certificate? When connecting, the SSL certificate is first: Connect to e.g. 123.example.com, which is subdomain covered by *.example.com Client connects to 123. example.com Server internally redirects to certificate of example.com SSL handshake incl...