By default, the server will bind to
0.0.0.0 on port
80 (unless otherwise configured). This IP is an alias meaning that it will be listening on all IPv4 addresses on the machine. Browse to either
http://127.0.0.1 if you’re on the same machine that’s running the server, or you can browse to any of the IPv4 addresses on the machine that’s running the server.
For example, if you set the
server_ip = "www.mydomain.com" and left
listen_ip = "0.0.0.0" and
listen_port = 80, then you can browse to
http://www.mydomain.com in your browser to access Apfell.
Browse to the server with any modern web browser. You will be automatically redirected to the
/login url. This url and
/register are the ones protected by
whitelisted_ip_blocks in the
The default username and password here is
All requests from the browser to the Apfell server are dynamic and based on the
listen_port you specified in the
Apfell uses JSON Web Tokens (JWT) for authentication. When you use the browser (vs the API on the command line), Apfell stores your access and refresh tokens in a cookie as well as in the local session storage. This should be seamless as long as you leave the server running; however, the history of the refresh tokens is saved in memory. So, if you authenticate in the browser, then restart the server, you’ll have to sign in again.