Recent content by Willy K.

I found a solution by myself - for everyone who's interested: My mistake was to the clients accesses test.my-domain:xxxxl, regardless if http or https, directly in meaning of that the webserver was bypassed entirely :rolleyes:. The only thing I need to do is to configure a reverse proxy in the...

I'm not sure, but maybe you have to do something in the domain settings before (in the "Domains & Websites" dashboard). I cant remember that I bought any subscriptions instead of choosing "Plesk Admin edition" when I rent the server from my provider, and I have options to deal with PHP in both...

Hello at all, I'm running Plesk Obsidian 18.0.35 on a Debian 10 system. The plan is to run a .NET Core application at some port, f.ex. http://my-domain.tld:1234 and https://my-domain.tld:4321, which is accessed by an React front-end application using fetch(). Since there is no official support...

Yes, it seems to be fixed - the problem did not occur any more during the last days. IMO the issue can be marked as fixed. @ahoi Do you agree? It ssems that I have no permission to set the issue to fixed? Maybe it must be done by the initator - i don't know...

Hello Ahai, seems that I'm (or you're) not alone. Below I'll try to be as exactly as possible on what I did. The short version is: I tried to reinstall from scratch as you did and ended up in the same troubles. If I remember right, this problems started about 2 days ago. Thehave no advise...