Swagger behind Nginx Proxy and CORS error

Newbie1 That's addressed a CORS issue, since the error appears to be from the server (unregistered device doesn't sound like any browser/web api error).

To support Authorization headers, you need to change from `*` to an explicit origin. You can confirm by trying a hardcoded one, and if that works you can figure out how to make it dynamic (with nginx).

Replace all instances with this...

add_header Access-Control-Allow-Origin: 'docs.swagger.example.com' always;