Forum Replies Created
-
Posts
-
Specify the report type
@ElasticRepas shown in the manual.In version 5, use only English characters in file path.
I am still ending up with the same bad gateway error.
What is in the nginx configuration related to Rapid SCADA?
Does http://localhost:10008 work?I’m concerned that the third link talks about “server blocks” which I felt like mostly didn’t apply to my install.
Before fix the bad gateway issue, I suggest to use the nginx configuration from the Rapid SCADA installation package.
Thank you for providing a solution.
New line is required. Also you can delete the existing file and create a new one. It should work.Is it possible to get rid of this mathcing time constraint ?
This is possible to make a time difference as a parameter. I’ve made a note in the back log. If you need it in time, we can do that on paid basis.
Hi,
In the module settings, the device 47 is specified. While in the Communicator you use the device 50. Probably, they must match.Hi,
Please check the terms.Hi,
Could you provide a screenshot of the Interface table?Do I have to fill the sample file with meaningful information that matches my installation – real existing channels etc.)?
This is not necessary for testing.
In the docs:
Install ASP.NET Core Runtime 8.0.xI recommend that the install docs get updated
I will check the docs.
I still get a bad gateway / 502 error
What is in the nginx configuration related to Rapid SCADA?
Does http://localhost:10008 work?According to the log file
2024-06-28 23:31:02 [hendra-ThinkPad-X220][root][ACT] User ScadaWeb is successfully authenticated
the web application works. It should be available directly at http://localhost:10008 on Linux.
