Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
INTRAWEB ACME
#15
(02-26-2024, 06:53 PM)JuergenS Wrote: Assuming your domain name is YourCompany.com, ACME will address your server at the following address:

http://YourCompany.com:80/.well-known/acme-challenge

But you don't have to set up the ./root/.well-known/acme-challenge directory!

Instead, you should set up the following directory:

C:\MyCompany\MayApplication.exe\acme-challenge

This directory must then also be specified in the Certificate Manager (Challenge Directory)

Intraweb probably has a handler installed for the original directory:

e.g: THandlers::Add(L"/.well-known/acme-challenge/", L"", new TIWClass_Acme());

If your company server has an Internet connection, then it should already have a domain name and a certificate and can be reached under
https://YourCompany.com
My company server is connected to the internet, but as I said, it is not a Web Server, his domain is not registered on the Web.
My intraweb app must be running on port 80, right?
My domain name is 'cpi.local' (I'm using local Active Directory domain). I created a Split DNS so that I can have a valid public suffix (TLD).
So, actually my subdomain is 'app.cpi.pt'.
Still getting the same timeout error.
I attached the servercontroller file for you to see if something is missing, please!!

(02-27-2024, 06:33 AM)Alexandre Machado Wrote: If you have an Indy or Http.sys server inside folder C:\MyApplication, the challenge directory should be:

C:\MyApplication\acme-challenge\

That's all you need. Drop the .well-known part.

Also, the IW certificate manager has a test button. Use it to verify if your server is responding correctly. If the IWCertManager can't access it correctly, likely Let's Encrypt servers can't do it either.

Ok, acme-challenge folder was created like you said.
My Intraweb app is running on port 80.
My Intraweb app is an Http.sys server. All done, like you said, in IWCertManager. When I hit the test button it gives "Domain test succeeded".
As I said to JuergenS, my Windows Server domain name is 'cpi.local' (I'm using local Active Directory domain). I created a Split DNS so that I can have a valid public suffix (TLD).
So, actually my subdomain is 'app.cpi.pt'.
I did deactivate the server antivirus program, add rules to the server firewall to accept income calls to port 80 and also tried to disable router firewall, but still getting the timeout error.
What can possible be blocking Let's Encrypt site to connect to my Windows Server?
Please advise!!
I attached the servercontroller file for you to see if something is missing, please!!


Attached Files
.zip   ServerController.zip (Size: 4.43 KB / Downloads: 1)
Reply


Messages In This Thread
INTRAWEB ACME - by JuergenS - 01-08-2020, 04:59 PM
RE: INTRAWEB ACME - by kudzu - 01-08-2020, 05:46 PM
RE: INTRAWEB ACME - by JuergenS - 01-09-2020, 08:03 AM
RE: INTRAWEB ACME - by Alexandre Machado - 01-09-2020, 08:33 PM
RE: INTRAWEB ACME - by JuergenS - 01-10-2020, 05:10 AM
RE: INTRAWEB ACME - by JuergenS - 07-10-2020, 08:00 AM
RE: INTRAWEB ACME - by Comograma - 02-23-2024, 03:43 PM
RE: INTRAWEB ACME - by Alexandre Machado - 07-13-2020, 10:28 AM
RE: INTRAWEB ACME - by JuergenS - 07-20-2020, 09:19 AM
RE: INTRAWEB ACME - by Alexandre Machado - 07-22-2020, 02:03 AM
RE: INTRAWEB ACME - by JuergenS - 02-23-2024, 08:41 PM
RE: INTRAWEB ACME - by Comograma - 02-26-2024, 05:56 PM
RE: INTRAWEB ACME - by Alexandre Machado - 02-27-2024, 06:33 AM
RE: INTRAWEB ACME - by JuergenS - 02-26-2024, 06:53 PM
RE: INTRAWEB ACME - by Comograma - 02-27-2024, 03:22 PM
RE: INTRAWEB ACME - by Alexandre Machado - 03-01-2024, 03:02 AM
RE: INTRAWEB ACME - by Comograma - 03-01-2024, 05:48 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)