HI,
No secret , I love URL logger, one of the things which took me some time was to configure SSL and then expose the ports on Internet so I can access it easily . Between Team ETL and me , I used acme , got SSL in place, they resolved some SSL bugs(they are very receptive to feedback) . It worked but now I have figured an even easier way to achieve this.
Why do you want a https name for url logger ? Simply because tonnes of service don't allow you to use http and why expose your server ip on the internet. Caddy also arranges for all SSL certificates, including subdomains freeing you from pain of win-acme and openssl
1. Enter CADDY. Download this from
HERE
. The primary advantage I feel is no ssl is required at your end , and no additional ports to be exposed to the world.
2. Extract Caddy , I have moved mine to C:\Caddy , feel free to put it where you want . create note file , call it CaddyFile, no extension. Open with notepad++.
3. In config file below , my URL logger is configured at port 4934.
Code:
{ storage file_system { root "C:\caddy" } } logger.mydomain.com { reverse_proxy localhost:4934 }
4. Go to your host , open domains and enter the ip of your server. I have configured mine with hosting. PS : the ip is random , no funny business.
5. Now run caddy with "c:\caddy\caddy.exe" run and you are SORTED
6. URL Logger will be configured without SSL mode
7. You can now access the Url Logger from browser anywhere with
logger.domain.com
8. It works on local machine , but as backup you can open on localhost:4934
If no-one of this make sense , let me know I will clarify or create loom video