After i make jwt token from web API and paste it on loraserver.toml and lora-app-server.toml this error gone. Thank you
But still, “Live LoRaWAN frame logs” and “Live event logs” statuses are disconnected.
I also use another lora server implementation on github, and sent payload from nodes can be show up.
Then that is probably the issue. Make sure your proxy is able to forward the websocket connections (including all the headers). I had issues when using Apache as a reverse proxy, but NGINX works fine (don’t forget to set a long timeout for the proxied requests, as else you will see disconnects after ~1 minute).
After one day running, i got this error on web ui
Error rpc error: code = OutOfRange desc = EOF (code: 11)
And Live frame logs become disconnected again
I upgrade my LoRa app server and Loraserver today after solving pagination problem, everything working except I got error in LoRa app Server in Log file
frame log time=“2018-04-12T01:07:29+05:30” level=info msg=“finished client streaming call” grpc.code=OK grpc.method=StreamFrameLogsForDevice grpc.service=ns.NetworkServer grpc.time_ms=0.033 span.kind=client system=grpc
And on web page : Error rpc error: code = OutOfRange desc = EOF (code: 11)
What is this error? Can I got some documentation where I can got meaning of this error code? What is solution of the problem?
I also get the “Live Frame Logs / Live Event Disconnected” message on the screen but there are no errors in the lora-app-server or loraserver log. How can I reconnect the services?
now I understand what kind of proxy you are talking about. I am using apache instead of NGINX. This is the current setting. I probably have to add the location part from the above NGINX setting?
ServerName lora.xxx.xxx
ServerAdmin hostmaster@xxx.xxx
ProxyRequests off
ProxyPreserveHost on
<Proxy *>
Order allow,deny
Allow from all
</Proxy>
ProxyPass / https://localhost:8080/
ProxyPassReverse / https://localhost:8080/
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined
ServerSignature On
SSLEngine on
SSLProxyEngine on #important for SSL support via proxy
Header set Strict-Transport-Security "max-age=15552000"
SSLCertificateFile /root/dehydrated/certs/lora.xxx.xxx/cert.pem
SSLCertificateChainFile /root/dehydrated/certs/lora.xxx.xxx/chain.pem
SSLCertificateKeyFile /root/dehydrated/certs/lora.xxx.xxx/privkey.pem
As I mentioned in a message a bit up, I never got the web-sockets working with Apache. You might want to switch to NGINX. If you do get it working, please share your configuration!
By default NGINX disconnects after one or two minutes (check the default values of these parameters) when there is no activity. As it is not guaranteed that you will receive or send a LoRaWAN frame each minute, you need to set this to a high value.
I switched to NGINX quickly and applied you config. But it seems like I still have an issue with the websocket. It is still disconnected even though the browser is now answering the request via the proxy of NGINX.
Is it possible I configured something wrong with the websockets?
I made it. I had to play around a bit but I finally got it working with apache. I had two issues, first thing I had to do is to upgrade my apache because it is still a 2.22 so I had to follow these two threads: