Your local server is using SSL/TLS encryption. To avoid security warnings in your browser, you may need a trusted certificate created with tools like mkcert
It is tempting to stick to standard HTTP ( http://localhost:11501 ) for local testing to avoid dealing with SSL certificates. However, using HTTPS locally prevents several critical production issues. 1. Browser Security Contexts https localhost 11501 url
While any application can be configured to use this port, one of the most common uses of localhost:11501 is in tutorials for installing and configuring a database server on CentOS 7. This configuration suggests that port 11501 might be set as a custom listening port for a database or another related local service. It's important to note that the default port for MariaDB (and MySQL) is 3306 ; using a non-standard port like 11501 can sometimes be done as a minor security measure or to run multiple instances. Your local server is using SSL/TLS encryption
The easiest way to handle local certificates is using mkcert , a simple tool that makes a locally-trusted development certificate. macOS (via Homebrew): brew install mkcert Windows (via Chocolatey): choco install mkcert Linux (Ubuntu/Debian): sudo apt install mkcert It's important to note that the default port
Follow these steps to get a fully trusted HTTPS server running on https://localhost:11501 .
Change your URL prefix to http:// or enable SSL in your app config.
: The exact method for configuring your server depends on the tools you use. Below are examples for some of the most popular setups.
