DmC

It runs an upload test before it gets enabled. If it popped up a green message it's working.

It's working. Clear your cookies and cache.

The second week is expiring tomorrow and I'm reporting first in line for transferring 😂😈

I had the same problem. They restrict outbound connections from the servers, so plesk (curl basically) is unable to initiate the remote connection to your ftp storage. Thus, it times out on the entering passive mode. One solution is for you to configure a specific passive port on the remote end that's already open here.Something I assume you can't do as you're not the administrator. The other solution is for @Krydos to add an exception rule for the ftpupload IP(s) on the firewall.

Usually, only disappointed/unsatisfied users will actively go to review without an explicit invitation . Ah human nature, it's lovely isn't it? It's not against their ToS to ask from people to review. Just that though, not "five star review and get more space", that is against their ToS 😂. I suggest send an email to users (with passing DMARC 😁) asking/inviting to objectively review Heliohost. https://support.trustpilot.com/hc/en-us/articles/13806607359762-2-Set-up-review-invitations-Free?current=1 @Krydos @wolstech

Donation for one additional GB ☺️ Transaction ID: 7XL77389AA448791D

I fixed the issue locally with this simple rule. Tested it and it works just fine.

Well I definitely think and the guy who commented on the request (attached), perfectly described what happened here. Wow though, I mean sure, Plesk isn't cP but there should be a limit, this one is kinda lol 😅 PS: Unfortunately, based on the number of votes, this won't happen.

That's about it, there aren't any more headers. Not on my Desktop client not on Roundcube webmail either. I know, I check headers every know an then, but in this particular case that's all it is. Maybe because the recipient is a local account? Technically my e-mail is a local one as far as tommy is concerned.

https://pastebin.com/YrCzpEYE

I deleted the certificate entirely and reissued a new one. Let's see

Hey there, I'm getting failure messages from Plesk. For some reason the automatic let's encrypt renewal tries to renew a certificate for underscore dot domain (_.domain.name) which results in error: Details: Type: urn:ietf:params:acme:error:rejectedIdentifier Status: 400 Detail: Invalid identifiers requested :

@Krydos it seems it's not fixed. I got another one (I'm opening another topic for this): Message-Id: <20241127214237.3FFA260064B2@tommy.heliohost.org

I see, I took for granted DNSSEC is present

Well I got this as a response sooo 😅