Deploy .NET to Docker - Revision history

Tom: /* Problems */

2025-09-19T04:28:34Z

‎Problems

2025-09-08T01:58:58Z

‎References

2025-09-06T01:30:24Z

‎Setting up a HTTPS connection

2025-07-29T20:26:32Z

‎Digital Ocean

2025-07-29T05:24:56Z

‎References

2025-07-29T01:54:37Z

‎Setting up a HTTPS connection

2025-07-29T01:51:14Z

‎Setting up a HTTPS connection

2025-04-27T17:52:21Z

‎Solutions

2023-01-08T21:53:36Z

‎Solutions

2022-01-01T00:06:25Z

‎Setting up a HTTPS connection

@@ Line 6: / Line 6: @@
 ==Problems==
-* Most sites now use [[Let's Encrypt]] Certificates which come with simple scripts for Apache, but no help for Windows.
+* Most sites now use [[Let's Encrypt]] Certificates which come with simple scripts for Apache on Nginx as primary web site or as reverse proxies, but no help for ASP.NET running native web server.
 ==Solutions==

@@ Line 63: / Line 63: @@
 -rw-r--r-- 1 root root   28 Apr 28 20:21  test.txt
   root@docker-s-1vcpu-1gb-sfo2-01:/home/app/TrustRegistry5/TrustRegistry/wwwroot/.well-known/acme-challenge#
 ==References==
 [[Category: Best Practice]]

@@ Line 32: / Line 32: @@
-  ; <<>> DiG 9.18.30-0ubuntu0.20.04.2-Ubuntu <<>> TXT _acme-challenge.trustregistry.u
+  ; <<>> DiG 9.18.30-0ubuntu0.20.04.2-Ubuntu <<>> TXT _acme-challenge.trustregistry.us
   ;; global options: +cmd
   ;; Got answer:

@@ Line 18: / Line 18: @@
 ** From the left side menu, click Access. Now use the console,or just reset the root password, which is typically less hassle even though you will need to change the p/w on first sign-in.
 * Once the root password is set just open a bash terminal on any computer and enter >>ssh root@000.000.000.000 << using the ip address of the droplet.
 ===Deploying the App via Github.com===

@@ Line 48: / Line 48: @@
   ssh root@165.227.49.50
 ==References==
 [[Category: Best Practice]]

@@ Line 29: / Line 29: @@
 * Set up letsencrypt
   dig TXT _acme-challenge.trustregistry.us @165.227.49.50
   ssh root@165.227.49.50

@@ Line 27: / Line 27: @@
 The lines shown below should work:
   cd /etc/letsencrypt/
 ==References==
 [[Category: Best Practice]]

@@ Line 9: / Line 9: @@
 ==Solutions==
 There are two distinct parts of the deployment and maintenance of the application plus a little bit of glue to stick one part to the other.
 * This example shows use on the DigitalOcean provider accessing it with [[SSH]].

@@ Line 10: / Line 10: @@
 ==Solutions==
 There are two distinct parts of the deployment and maintenance of the application plus a little bit of glue to stick one part to the other.
-* This example shows use on the DigitalOcean provider accessing it with ssh.
+* This example shows use on the DigitalOcean provider accessing it with [[SSH]].
 * DigitalOcean Droplets are Linux-based virtual machines (VMs) that run on top of virtualized hardware.
 * The default username is root on most operating systems, like Ubuntu and CentOS.

@@ Line 23: / Line 23: @@
 ===Setting up a HTTPS connection===
 This section shows the use of [[Let's Encrypt]] certificates, which have a life of just 3 months, but is free.  Other sites have a life of one year but charge money. Two-year certificates are no longer acceptable to many browsers.
+* See the wiki page [[Let's Encrypt]] for more details.
-The line shown below should work
+The lines shown below should work:
 ==References==
 [[Category: Best Practice]]