Skip to content

Connecting to Server

Before using Expose, you need to connect the app to your server.

Initial Setup

  1. Open Expose from your Applications folder
  2. Click the menu bar icon → Open Dashboard
  3. Go to Settings (gear icon)
  4. Click the Account tab

Server Configuration

Enter your server details:

FieldValueExample
API Server URLYour server’s API endpointhttps://api.yourdomain.com
Tunnel DomainYour tunnel subdomainexpose.yourdomain.com

Creating an Account

If you don’t have an account yet:

  1. Enter your server URL
  2. Click Create Account
  3. Enter your email and password
  4. Click Register

Your account is created and you’re automatically logged in.

Signing In

If you already have an account:

  1. Enter your server URL
  2. Click Sign In
  3. Enter your email and password
  4. Click Login

API Key

After signing in, you need an API key to use tunnels:

  1. Go to SettingsAccount
  2. Click Create API Key
  3. Give it a name (e.g., “MacBook Pro”)
  4. Copy the key immediately — you won’t see it again

The API key is saved automatically and used for all tunnel connections.

Testing Connection

To verify everything works:

  1. Go to the Projects tab
  2. You should see your configured scan directories
  3. If projects are detected, the connection is working

Multiple Servers

Currently, Expose supports connecting to one server at a time. To switch servers:

  1. Go to SettingsAccount
  2. Click Sign Out
  3. Enter the new server URL
  4. Sign in with your credentials for that server

Troubleshooting

Connection Failed

  • Verify the server URL is correct (include https://)
  • Check your internet connection
  • Ensure the server is running: curl https://api.yourdomain.com/health

Invalid Credentials

  • Double-check your email and password
  • Try resetting your password

API Key Not Working

  • Ensure the key was copied completely
  • Try creating a new API key
  • Check the key hasn’t been revoked

Certificate Errors

  • Ensure your server has valid TLS certificates
  • Check certificate hasn’t expired
  • Verify DNS is configured correctly