Search results

The domain not resolving has fixed itself eventually. Just took a little longer for the nameservers i guess. The remaining issue was with SSL not working. Due to not hosting domain.tld it wasn't possible to secure the mailserver with its own ssl certificate. Email client had to be adjusted to...

The nameservers are external ones yes but they share the same hostname "webhost.be", and "webhost.be" is myself. Just seems to have taken unusually long. The webmail route is active now, but as expected now throws an SSL error that the existing certificate is only valid for "pl1.webhost.be" and...

I have this domain that's a bit "unusual" that needed to be transferred, but now for some reason webmail won't resolve. The website itself is hosted on squarespace, previous registrar was nameweb and they paid extra for 1 mailbox. Previous registrar webmail was online via imapweb.nameweb.biz...

No newer update thatn KB5018496 on W11 Pro 22H2

Looks like i was slightly outdated, wasn't notified yet. Manual check found KB5018496, tried switching to modern again. No effect, still the same SSL error. Supposed KB5018493 is not found

Reported this issue here in early july. Running W11 Pro x64 22H2, outlook 365 and windows fully up to date (incl outlook preview now switch enabled in top right) KB5018418, KB5018410, KB5018493 not listed under windows updates. The earlier links provided don't work wince its w11. I found...

Guess i'll have to leave it on intermediate then. Cause i'm running W11 22H2, outlook fully up to date and modern still won't work.

Ugh again no mail from the forum. Sorry for the delay. Outlook is indeed by microsoft, but TLS type is managed at the plesk level, hence coming here. No clue why it worked before, then stopped working and only works if i drop the TLS level. If mods think there's a better place, i'm open to get...

1st reply 4 months. Guess this forum isn't super active. Totally forgot about this. 1st & 2nd solution: that's not a solution, that's avoiding the problem. I am not compromising my system security by uninstalling security updates.

While doing some routine maintenance on my server, i checked things in SSL it! and saw that the last cypher sync was from january last year. Current settings are "Modern" and everything worked fine up until the sync. After the sync i just did, outlook refuses to connect over secure ports and i...

that link already used the hostname. So created a new user, set it to self-activate. Good news and bad news. The good news: something changed and {{ get_password_link }} is now properly filled in. The bad news: {{ hostname }} still gets filled in, but is no longer a hotlink like it was before

how do i generate such an e-mail without creating a new user? (and if it doesn't change anything, undo that command)

4 min edit timer limit lol. When i run a search on the server IP used by the {{ get_password_link }} and shown in the panel i get the following results 266 entries in dns_recs 1 entry in IP_Addresses 2 in log_components 1 in PleskStats 32 in SecretKeysIpAddresses

Nope returns the hostname pl1.<domain>.<tld>:8443 yet the {{ get_password_link }} returns server ip

It very much still persists. I (and followup posts) said this on March 4th.

In mine that variable isn't being populated AT ALL, it pulls the server IP, which then obviously when clicked on, triggers an SSL security warning as certificates are assigned on hostname not IP. The {{ hostname }} does get properly filled in, so it's an issue with the specific {{...

It shouldn't contain a hostname, just that variable. That's in your case problem nr 1. Plesk then SHOULD in normal behavior automatically fun in the proper hostname on-the-fly when that template gets triggered. It doesn't, that's problem nr 2, which we both have. That variable pulls the server...

They shouldn't need regenerating, this is a bug in plesk/how the templates process variables. {{ get_panel_link }} pulls the server IP, not the hostname.

So i need to resurrect this (google search led me to this). Server properly has a hostname set. Just noticed this same problem myself on "customer account creation" e-mails too. As admin i ALWAYS login on via hostname, never IP, since the server is properly secured with a Let's Encrypt...

No, i specifically said i was still looking for an easy way to spot the difference in my previous post