!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

207 Members
58 Servers

Load older messages


SenderMessageTime
11 Nov 2023
@c0ba1t:matrix.orgCobaltOkay, then nginx won't run any command. Your config only describes reverse proxy that redirects all requests (for the vhost) to the (presumable) service running on port 5173.21:53:36
@c0ba1t:matrix.orgCobaltPresumably, the systemd service starts a server on localhost:5137?21:55:22
@peter-lustig:matrix.orgpeter-lustig
In reply to @c0ba1t:matrix.org
Presumably, the systemd service starts a server on localhost:5137?
yeah
21:56:36
@c0ba1t:matrix.orgCobaltOkay, then that should work. If the systems service starts you should be good to go from the NodeJS side.21:57:36
@peter-lustig:matrix.orgpeter-lustig
In reply to @c0ba1t:matrix.org
Okay, then that should work. If the systems service starts you should be good to go from the NodeJS side.
so you think what I have is correct?
21:57:52
@c0ba1t:matrix.orgCobaltMaybe? You have only posted an excerpt from an NGINX vhost config with an `example.com` domain and a systemd unit. 21:59:49
@c0ba1t:matrix.orgCobaltBut it looks correct22:00:01
@peter-lustig:matrix.orgpeter-lustig
In reply to @c0ba1t:matrix.org
Maybe? You have only posted an excerpt from an NGINX vhost config with an `example.com` domain and a systemd unit.
ok but I think that root = is useless then
22:04:53
@peter-lustig:matrix.orgpeter-lustigi need proxypass for the backend though right?22:06:42
@c0ba1t:matrix.orgCobaltYes22:08:33
@c0ba1t:matrix.orgCobaltDepending on the service you might also want `services.nginx.virtualHosts.<name>.locations.<name>.recommendedProxySettings` and `services.nginx.virtualHosts.<name>.locations.<name>.proxyPass`22:10:43
@c0ba1t:matrix.orgCobalt* Depending on the service you might also want `services.nginx.virtualHosts.<name>.locations.<name>.recommendedProxySettings` and `services.nginx.virtualHosts.<name>.locations.<name>.proxyPass`22:10:52
@c0ba1t:matrix.orgCobalt* Depending on the service you might also want `services.nginx.virtualHosts.<name>.locations.<name>.recommendedProxySettings` and `services.nginx.virtualHosts.<name>.locations.<name>.proxyWebsockets`22:11:11
12 Nov 2023
@peter-lustig:matrix.orgpeter-lustig ok Cobalt getting it started to fail 01:14:37
@peter-lustig:matrix.orgpeter-lustigthe systemd service01:14:39
@peter-lustig:matrix.orgpeter-lustig unfortunately there are no closer details01:14:45
@peter-lustig:matrix.orgpeter-lustig but I get bad gateway on nginx 01:16:50
@peter-lustig:matrix.orgpeter-lustigso idk01:16:53
@peter-lustig:matrix.orgpeter-lustigplease help if you have an idea01:53:06
@c0ba1t:matrix.orgCobaltThe NGINX bad gateway error is NGINX's way of reporting that it couldn't reach the service behind proxy pass.08:17:05
@c0ba1t:matrix.orgCobalt
In reply to @peter-lustig:matrix.org
the systemd service
You might want to look into the journal (journalctl -xeu ) to inspect your app logs.
08:18:18
@c0ba1t:matrix.orgCobalt* In reply to @peter-lustig:matrix.org the systemd service If your app öogs to stderr/stdout, you might want to look into the journal (journalctl -xeu ) to inspect your app logs08:19:24
@c0ba1t:matrix.orgCobalt* In reply to peter-lustig the systemd service If your app logs to stderr/stdout, you might want to look into the journal (journalctl -xeu ) to inspect your app logs 08:19:51
@peter-lustig:matrix.orgpeter-lustig
In reply to @c0ba1t:matrix.org

In reply to peter-lustig
the systemd service

If your app logs to stderr/stdout, you might want to look into the journal (journalctl -xeu ) to inspect your app logs

Yes, I am aware of that. But journalctl for the service only gives me `The unit has entered the 'failed' state with result 'exit-code'
13:10:21
@peter-lustig:matrix.orgpeter-lustig but i execute the command PORT=5173 node . and if I test that locally everything just works 13:11:59
@peter-lustig:matrix.orgpeter-lustig

Here is my current systemd service:

systemd.services.myservice = {
    wantedBy = ["multi-user.target"];
    after = ["network-online.target"];
    serviceConfig = {
      Type = "simple";
      ExecStart = "PORT=5173 ${pkgs.nodejs_20}/bin/node .";
      WorkingDirectory = inputs.myservice.packages.${pkgs.system}.default;
      Restart = "always";
    };
  };
13:17:00
@c0ba1t:matrix.orgCobaltOkay, have you tried going to the workingdirectory and executing node there?13:19:10
@lily:lily.flowersLily Foster POST=5173 is not a command 13:19:20
@lily:lily.flowersLily Foster If you are trying to set an environment variable, set Environment = "PORT=5173 13:19:31
@lily:lily.flowersLily Foster * If you are trying to set an environment variable, set Environment = "PORT=5173" 13:19:33

Show newer messages


Back to Room ListRoom Version: 6