Unable to configure proxy with puma socket

Help
21

@matt I currently have file_server first

  encode gzip
  log stdout
  root * /home/deploy/apps/rails-app/current/public
  file_server /assets/* {
    root /home/deploy/apps/rails-app/current/public/assets
  }
  reverse_proxy {
    to unix//home/deploy/apps/rail-app/shared/tmp/sockets/rails-app-puma.sock
 #   transparent
 #   websocket
 #   policy round_robin
  }
  # errors stdout
  header / {
        Strict-Transport-Security "max-age=31536000"
  }

  #proxy /solr localhost:8983 {
  #  transparent
  #}
}
22

Doesn’t matter if it’s not in a route :slight_smile: Please at least click the links and read the docs I linked you to. It will help you.

Edit: See this guy’s solution to a similar problem, it’s a good use of the handle directive, which can be used similarly to solve your problem: hostname appears in more than one automation policy · Issue #3351 · caddyserver/caddy · GitHub

23

That did it

24

FYI for formatting config/code, use ``` on a line before and after your config blocks.