Forum Replies Created
-
Posts
-
Hi,
Archive configuration is displayed when you open its properties.
Log files are located in SCADA\ScadaServer\Log directory. You should enable the detailed log in the archive properties.Hi,
I’m good. Thank you. Hope you are well too.
You could try to run ScadaAdmin by the command
dotnet ScadaAdmin.dll
to be sure that it is not run under Mono.Is it on Windows?
.NET 6 is not required.
Can the compiled assembly be run with dotnet-runtime-6 or also requires runtime-8 ?
An assembly can be compiled to support several runtimes. Rapid SCADA applications since v6.2 require .NET 8.
Hello,
According to the screenshot, the compressed size of the project is more than 350 MB which is probably too heavy.
I suggest the following:
1. Open the project folder in Windows file explorer.
2. Search for all files of the project, display them as a table and sort by size.
3. Make a screenshot of the biggest file names and sizes.Hello,
Perform the list item #10 from the manual.Download ScadaTestClient and try to connect to Server with different usernames: ScadaComm and ScadaWeb. Usernames are set in ScadaTestClient.xml
Could you open the project SCADA\ProjectSamples\HelloWorld\HelloWorld.rsproj in the Administrator app and upload again?
Hi,
> 2024-02-09 09:35:24 [tomasz-Latitude-5480][root][INF] The application is ready for operating
This line means that the web application works correctly. You should check the nginx configuration. Check that you performed the item 5c described here.The Communicator application successfully connects to Server. However, the web app cannot connect.
Please copy what is written in Webstation log, ScadaWeb.log?Hello,
Do you use Linux?
Please open the Administrator application, open the HelloWorld project and check the log file of the Webstation application.
Or just find logs in the file system and check ScadaWeb.log.Note that you can find similar security reports for any well known SCADA software. Since Rapid SCADA is open source, its internal structure has been tested by many professional developers and we respond to their feedback.
There are many Rapid SCADA instances available on the Internet that work reliably for many years.
What you should do to protect the system:
1. Follow the safety recommendations.2. Restrict access to your project. It’s recommended to store project on GIT in private repository. It helps to control any changes made in the project.
If an attacker changed your project, he could access the server’s filesystem by read and write operations from the scripts. Also he could add hyperlinks to external resources on the schemes.3. Restrict access to the production server. It’s obvious.
Use firewall.4. If Rapid SCADA is hosted in the cloud, enable captcha and use Guard Plugin for additional security.
5. Use strong passwords in production environment. Change all default passwords.
6. Run Rapid SCADA services with lower privileges instead of system (root) user.
