cody on Nostr: First of all, I'm glad you chose to run nostr-relay-nestjs! Since you've confirmed ...

First of all, I'm glad you chose to run nostr-relay-nestjs!

Since you've confirmed that the /metrics endpoint is accessible, I believe you've successfully got it up and running, and you're able to access it in some way. Therefore, your relay address would be ws(s)://<ip address or your host name>:<port>

Nostr relay is a WebSocket-based service, so the protocol used is ws(s):// rather than http(s)://

If you're unable to establish a WebSocket connection but can make HTTP requests, I suspect your NGINX configuration might be incorrect. Here's a simple NGINX configuration for a WebSocket service:

```
server {
server_name xxxxx;
location / {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:port;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
}
}
```

If you want to make your relay more easily accessible to others, you can purchase a domain and register DNS through a service like Cloudflare to forward requests to your AWS server.