Start it behind proxy

[umsmin]

I tried to run it behind a nginx proxy on one of my vm. It runs as a service with this script

[Unit]
Description=PineSAM Server for Pinecil Soldering Iron
After=network.target bluetooth.target
Requires=network.target bluetooth.target

[Service]
Type=simple
ExecStart=/var/www/PineSAM/PineSAM

[Install]
WantedBy=multi-user.target

I reach it direct with as http://123.456.789.012:8080. No problem all working as espected.

The first time after nginx configuration as proxy it also works. Later I tried it again and no way without any clue it doesn't work again.

Here my proxy-config

server {
listen       443 ssl;
server_name  sub.domain.com;



    ssl_certificate /etc/xyz/fullchain.cer;
    ssl_certificate_key /etc/xyz/xyz.key;


    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";`
    }
}

He show the PineSAM screen and in the top area a rotating circle, but without themperature or other values.

When I make
systemctl status PineSAM.service
This is the result:

Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.186::INFO::Sending response          ws_server.py:156
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.187::INFO::Connection closed         ws_server.py:174
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.189::INFO::connection closed            server.py:264
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.323::INFO::Sending response          ws_server.py:156
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.324::INFO::Connection closed         ws_server.py:174
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.325::INFO::connection closed            server.py:264
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.454::INFO::Sending response          ws_server.py:156
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.456::INFO::Got message:              ws_server.py:151
Feb 02 21:53:27  PineSAM[1434]:                   {"command":"GET_INFO"}
Feb 02 21:53:27  PineSAM[1434]:          INFO     21:53:27.700::INFO::Sending response          ws_server.py:156

[builder555]

i've never tried running it behind a proxy, but it looks like websocket connection fails to establish. are you seeing any errors in browser console?

[umsmin]

I get it sometime running without Proxy but PineSAM crashes after a sometimes minutes or seconds.

Feb 15 20:01:04 workshop systemd[1]: Started PineSAM.service - PineSAM Server for Pinecil Soldering Iron.
Feb 15 20:01:04 workshop PineSAM[2273]: 20:01:04 INFO     20:01:04.706::INFO::Starting websocket server ws_server.py:137
Feb 15 20:01:04 workshop PineSAM[2273]:                   on 0.0.0.0:8080
Feb 15 20:01:04 workshop PineSAM[2273]:          INFO     20:01:04.710::INFO::Starting pinecil     pinecil_monitor.py:40
Feb 15 20:01:04 workshop PineSAM[2273]:                   monitor
Feb 15 20:01:04 workshop PineSAM[2273]:          INFO     20:01:04.711::INFO::looking for          pinecil_monitor.py:43
Feb 15 20:01:04 workshop PineSAM[2273]:                   pinecil...
Feb 15 20:01:04 workshop PineSAM[2273]:          INFO     20:01:04.712::INFO::looking for          pinecil_monitor.py:21
Feb 15 20:01:04 workshop PineSAM[2273]:                   pinecil...
Feb 15 20:01:04 workshop PineSAM[2273]:          INFO     20:01:04.713::INFO::Detecting "pinecil"...           ble.py:20
Feb 15 20:01:04 workshop PineSAM[2273]:          INFO     20:01:04.732::INFO::server listening on          server.py:706
Feb 15 20:01:04 workshop PineSAM[2273]:                   0.0.0.0:8080
Feb 15 20:01:09 workshop PineSAM[2273]: 20:01:09 INFO     20:01:09.747::INFO::Found pinecil at                 ble.py:25
Feb 15 20:01:09 workshop PineSAM[2273]:                   C8:90:A8:21:33:0B
Feb 15 20:01:09 workshop PineSAM[2273]:          INFO     20:01:09.750::INFO::Connecting to        pinecil_monitor.py:50
Feb 15 20:01:09 workshop PineSAM[2273]:                   pinecil...
Feb 15 20:01:09 workshop PineSAM[2273]: Traceback (most recent call last):
Feb 15 20:01:09 workshop PineSAM[2273]:   File "main.py", line 75, in <module>
Feb 15 20:01:09 workshop PineSAM[2273]:   File "asyncio/runners.py", line 190, in run
Feb 15 20:01:09 workshop PineSAM[2273]:   File "asyncio/runners.py", line 118, in run
Feb 15 20:01:09 workshop PineSAM[2273]:   File "asyncio/base_events.py", line 654, in run_until_complete
Feb 15 20:01:09 workshop PineSAM[2273]:   File "main.py", line 64, in main
Feb 15 20:01:09 workshop PineSAM[2273]:   File "pinecil_monitor.py", line 52, in monitor
Feb 15 20:01:09 workshop PineSAM[2273]:   File "pinecil/pinecil.py", line 131, in connect
Feb 15 20:01:09 workshop PineSAM[2273]:   File "pinecil/pinecil.py", line 113, in __set_ble_uuids_based_on_version
Feb 15 20:01:09 workshop PineSAM[2273]:   File "pinecil/ble.py", line 99, in get_characteristics
Feb 15 20:01:09 workshop PineSAM[2273]: Exception: Could not find service f6d75f91-5a10-4eba-a233-47d3f26a907f
Feb 15 20:01:09 workshop PineSAM[2273]: [PYI-2273:ERROR] Failed to execute script 'main' due to unhandled exception!
Feb 15 20:01:09 workshop systemd[1]: PineSAM.service: Main process exited, code=exited, status=1/FAILURE
Feb 15 20:01:09 workshop systemd[1]: PineSAM.service: Failed with result 'exit-code'.
Feb 15 20:01:09 workshop systemd[1]: PineSAM.service: Consumed 681ms CPU time, 90M memory peak.

With the direct connection it shows me the Pinecil on webscreen. Also the status about connection. Behind the proxy it shows me the screen with a rotating circle in top of the screen but nothing about connection or loss.

[umsmin]

One big improvement about stability for PineSAM as a Service I discovered is the Bluetooth Stick. Today I get a new one with V6 Bluetooth and two antennas. Before the connection was breaking away when I put the Iron more than around one meter away from the Adapter. With the new one, okay my office is to small but 3 meters are no problem. Absolutely stable.

But the problem about the proxy exists. The console shows me

PineSAM[999]:          INFO     19:46:23.649::INFO::connection closed            server.py:264
PineSAM[999]:          INFO     19:46:23.782::INFO::connection rejected (200 OK) server.py:229