# Autoxpose

Autoxpose is an automatic DNS and reverse proxy manager for Docker containers that creates encrypted proxy routes without manual setup. It is open source and self-hosted, installable on TrueNAS.

Canonical page: https://ourlocalhost.com/app/3720/autoxpose

## Description

Autoxpose is an automatic DNS and reverse proxy manager for Docker containers that creates encrypted proxy routes without manual setup.

## Platform availability

Available on 2 of 10 platforms: TrueNAS, ZimaOS.

## Health score

66/100 (Good), based on 4 of 5 factors.
- Maintained: 82 (last commit 44 days ago)
- Popular: 44 (152 GitHub stars)
- Easy to install: 35 (2 install platforms, install notes)
- Security check: 94 (no serious findings, 1 minor, CI, tests)

## Links

- TrueNAS: https://apps.truenas.com/catalog/autoxpose/
- GitHub: https://github.com/mostafa-wahied/autoxpose

## Common questions

### What Docker label prefix does Autoxpose use to detect containers it should expose?

Set labelPrefix to autoxpose so Autoxpose can find the containers you want to expose. If the prefix is wrong, it will not see those apps.

### What IP and port settings need to be correct before Autoxpose starts?

Set your public IP as serverIp and your LAN IP as lanIp, and open port 3000 for Autoxpose's HTTP access. If these are wrong or closed, Autoxpose may be unreachable or create DNS and proxy entries that do not work.

### Where does Autoxpose store its state, and why should that file be backed up?

Autoxpose saves state at database.path, defaulting to ./data/autoxpose.db. Losing that file can force service re-detection and leave orphaned entries, so keep it on backup storage.

### Does Autoxpose set up SSL when configuring the reverse proxy?

Yes, after you add a label to a container, Autoxpose creates the DNS record and configures the reverse proxy with SSL.

---
Source: Our Local Host (https://ourlocalhost.com/app/3720/autoxpose), the self-hosted and open-source app directory.
