When setting up a local network, it's common to use self-signed HTTPS certificates on default IP addresses. While this can provide a certain level of protection against data tampering, it may not be adequate for all scenarios. There are several approaches to consider:
1. Using a self-signed IP certificate: While browser warnings can be disregarded, self-signed certificates can cause issues when making API requests via HTTPS, resulting in errors.
2. Utilizing an actual domain name:
2.1 Resolving the domain name to a local IP address: However, this approach is not recommended as each network environment is unique, and resolving a domain name to an unknown IP address can be problematic.
2.2 Resorting to local DNS resolution: This would require modifying hosts files or DNS servers on each machine, which can be cumbersome.
It appears that there may not be a convenient solution to this issue.