Expose the intranet service with Peanut Shell + HTTPS (non-443 port)

Mar 18, 2023166

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

To meet basic requirements for setting up a public server, one needs a public IP address, a top-level domain name from Peanut Shell, and a public IP server. The process involves downloading and launching the Peanut Shell client on the public IP server, obtaining an HTTPS certificate, and configuring the local Nginx server with the obtained signature and domain name. Finally, the local Nginx server should be set to a non-443 port and mapped to the public server's port for successful proxy access.

Basic Requirements

1. Public IP
1. Peanut shell top-level domain name
1. Public IP server

Steps

1. Download the Peanut Shell client on the public IP server and start it. When the top-level domain name is resolved to this server, apply for an HTTPS certificate. Peanut shell does not support DNS validation, so file validation is required. Place the validation file provided by the service operator. After successful validation, obtain the signature.
1. Configure the signature and domain name in the local Nginx, turn off the Peanut Shell client on the public server, open DDNS on the local router, or start the local Peanut Shell client.
1. The local Nginx uses a non-443 port, then NAT maps out, for example, local 1443, mapped to 1443 (to avoid unnecessary complications, it's best to use the same port).

Without any issues, accessing https://domain.xxx:1443 should be able to proxy in.