Peanut shell + https (non-443 port) exposes the internal network service.

Mar 18, 202321

AI Translation

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

AI-generated summary

The basic requirements for this process are a public IP, a top-level domain from Peanut Shell, and a public IP server. The steps involve downloading and starting the Peanut Shell client on the public IP server, applying for an HTTPS certificate when the top-level domain is resolved to this server, setting up the signature and domain in the local Nginx, and opening DDNS or starting the local Peanut Shell client on the local router. The local Nginx should be configured to use a non-443 port and then mapped to the same port externally. This should allow access to the domain with HTTPS on port 1443.

Basic Requirements

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

Steps

1. Download and launch the Peanut Shell client on the public IP server. When the top-level domain name is resolved to this server, apply for an HTTPS certificate. Peanut Shell does not support DNS verification, so file verification is required. Therefore, place the verification file provided by the service operator. Once the verification is successful, obtain the signature.
1. Configure the signature and domain name in the local Nginx on the intranet. Close the Peanut Shell client on the public IP server and enable DDNS on the local router or launch the local Peanut Shell client.
1. Configure the local Nginx to use a non-443 port, and then perform NAT mapping, for example, use port 1443 locally and map it to 1443 externally (to avoid unnecessary complications, it is best to use the same port).

If everything goes well, accessing https://domain.xxx:1443 should be able to proxy in.