Unable to open tutor even after everything working

Site Operators Tutor Help
1

I got ‘tutor local start‘ to work but when I open localhost absolutely nothing shows up. But in the cmd I get this

caddy-1        | 
{
  "level": "info",
  "ts": 1755723018.5049682,
  "logger": "http.log.access",
  "msg": "handled request",
  "request": {
    "remote_ip": "192.168.65.1",
    "remote_port": "54524",
    "client_ip": "192.168.65.1",
    "proto": "HTTP/1.1",
    "method": "GET",
    "host": "localhost",
    "uri": "/favicon.ico",
    "headers": {
      "Sec-Ch-Ua-Mobile": [
        "?0"
      ],
      "Accept": [
        "image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8"
      ],
      "Referer": [
        "http://localhost/"
      ],
      "Sec-Ch-Ua": [
        "\"Not;A=Brand\";v=\"99\", \"Google Chrome\";v=\"139\", \"Chromium\";v=\"139\""
      ],
      "Sec-Fetch-Mode": [
        "no-cors"
      ],
      "User-Agent": [
        "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36"
      ],
      "Sec-Fetch-Site": [
        "same-origin"
      ],
      "Sec-Fetch-Dest": [
        "image"
      ],
      "Connection": [
        "keep-alive"
      ],
      "Sec-Ch-Ua-Platform": [
        "\"macOS\""
      ],
      "Accept-Encoding": [
        "gzip, deflate, br, zstd"
      ],
      "Accept-Language": [
        "en-US,en;q=0.9,hi;q=0.8"
      ]
    }
  },
  "bytes_read": 0,
  "user_id": "",
  "duration": 0.000008416,
  "size": 0,
  "status": 0,
  "resp_headers": {
    "Server": [
      "Caddy"
    ]
  }
}

Any help would be greatly appreciated

2

Hi @Imaad_Thouheed and welcome to the community. Have you followed the instructions in https://docs.tutor.edly.io/ ? Following AI instructions often doesn’t work. What version of Tutor are you running?

3

Hi @Imaad_Thouheed

As Sarina mentioned, checking the docs would be a great place to start, in particular it sounds like you need to configure DNS records for your server.

localhost is really just an alternative name for 127.0.0.1 which means the same computer you’re on (ie every computer in the world is localhost to itself)

The way Caddy works is as a proxy between you and your server’s containers, so in order for your web page to be served to you Caddy needs to know what service you are requesting, which is done using the DNS name.

For example if you own the domain mydomain.com and you wanted your server to be accessible on learn.mydomain.com then you need DNS entries for learn.mydomain.com and *.learn.mydomain.com to point back to your server IP address. If you’re just accessing this internally on your own network for now then you can add these to your internal DNS server so they point back to the LAN IP of your tutor server. Once/if you want to make it publicly accessible over the internet then you’ll need the same records (but pointing back to your WAN IP) at the name servers configured with your domain’s registrar (along with port forwarding/reverse proxy/etc at your firewall/router between your LAN/WAN)