[GUIDE]How To Install Silkroad Online R Private Server ISRO-R Version Full Setup

Quote:

Originally Posted by omar0101 hello, i setup everything and its all green and working, but when i try to login it says "you aren't a registered member with rigid" .

Quote:

Originally Posted by Skipper159 Same Problem, anyone has an answer?

USE SILKROAD_R_ACCOUNT
GO
exec _Rigid_Register_User 'ID', 'password in MD5', 'email' , 'US' , '127.0.0.1'

Quote:

Originally Posted by autoamticasd I used different appsettings.json config in Billing folder Example i used is below: (change ip to your server ip below and password of the sa user) { "Logging": { "LogLevel": { "Default": "Information", "Microsoft.AspNetCore": "Warning", "Microsoft.EntityFrameworkCore": "Warning" }, "File": { "Path": "BillingLog.txt", "Append": true, "MinLevel": "Trace", "FileSizeLimitBytes": 10240, "MaxRollingFiles": 5 } }, "Kestrel": { "EndPoints": { "Http": { "Url": "http://0.0.0.0:18080" } } }, "AuthService": "Simple", "DbConfig": { "AccountDB": "Data Source=.\\;TrustServerCertificate=True;Initial Catalog=SILKROAD_R_ACCOUNT;User ID=sa;Password=1;", "JoymaxPortalDB": "Data Source=.\\;TrustServerCertificate=True;Initial Catalog=GB_JoymaxPortal;User ID=sa;Password=1;" }, "NotificationService": { "Type": "Email" }, "NationPingService": { "ListenAddress": "0.0.0.0", "ListenPort": 12989 }, "EmailService": { "From": "yourEmail", "FromFriendlyName": "YourServerName??", "SmtpServer": "smtp.gmail.com", "UseSSL": true, "Port": 465, "Username": "FOLLOW https://code-maze.com/aspnetcore-send-email/", "Password": "FOLLOW https://code-maze.com/aspnetcore-send-email/", "SkipTokenValidation": false }, "ServiceCompany": 11, "RequestTimeoutSeconds": 60, "PortalCGIAgentHeader": "Portal_CGI_Agent", "SaltKey": "eset5ag.nsy-g6ky5.mp", "AllowedHosts": "*" }

Quote:

This JSON configuration file is used for an ASP.NET Core server ). Below is a clear explanation of each section: - **Logging**: Defines how logs are handled. - `"Default": "Information"` means the default log level shows information messages. - `"Microsoft.AspNetCore": "Warning"` and `"Microsoft.EntityFrameworkCore": "Warning"` reduce log noise from the framework. - `"File"` section defines a log file named `BillingLog.txt` that records trace-level logs, appends new logs, and keeps up to 5 rolling files. - **Kestrel**: Sets up the web server endpoint. - `"Url": "http://0.0.0.0:18080"` means the server listens on all IPs at port **18080**. - **AuthService**: Specifies the type of authentication used. Here it's `"Simple"`, meaning basic or custom authentication. - **DbConfig**: Contains the connection strings for the SQL Server databases. - `AccountDB` connects to `SILKROAD_R_ACCOUNT`. - `JoymaxPortalDB` connects to `GB_JoymaxPortal`. Both use SQL authentication with user `sa` and password `1`. - **NotificationService**: Defines the type of notification system used — `"Email"`. - **NationReminderService**: Handles a service that listens on IP `0.0.0.0` and port `12989`. It’s typically used for inter-server communication or reminders in Silkroad server architecture. - **EmailService**: Defines SMTP settings for sending emails. - `smtp.gmail.com` is the SMTP server. - SSL is enabled (`"UseSSL": true`) on port 465. - The username and password fields currently contain placeholder text from a tutorial link. - `"SkipTokenValidation": false` ensures email tokens are validated. - **ServiceCompany**, **RequestTimeoutSeconds**, **PortalCGIAgentHeader**, and **SaltKey**: - `ServiceCompany: 11` is an internal identifier for the company/service type. - `RequestTimeoutSeconds: 60` sets a 60-second timeout for requests. - `PortalCGIAgentHeader` defines a header name for communication between services. - `SaltKey` is used for encryption or password hashing. - **AllowedHosts**: `"*"` allows all hosts (used during development). **Important corrections made:** 1. Fixed invalid `Data Source=.\\;` → changed to `Data Source=.;` 2. Renamed `"NationPingService"` to `"NationReminderService"` for correct service recognition. 3. Verified all commas and syntax are valid JSON. This configuration file is now valid, readable by ASP.NET Core, and ready for deployment.

Quote:

{ "Logging": { "LogLevel": { "Default": "Information", "Microsoft.AspNetCore": "Warning", "Microsoft.EntityFrameworkCore": "Warning" }, "File": { "Path": "BillingLog.txt", "Append": true, "MinLevel": "Trace", "FileSizeLimitBytes": 10240, "MaxRollingFiles": 5 } }, "Kestrel": { "EndPoints": { "Http": { "Url": "http://0.0.0.0:18080" } } }, "AuthService": "Simple", "DbConfig": { "AccountDB": "Data Source=.;TrustServerCertificate=True;Initial Catalog=SILKROAD_R_ACCOUNT;User ID=sa;Password=1;", "JoymaxPortalDB": "Data Source=.;TrustServerCertificate=True;Initial Catalog=GB_JoymaxPortal;User ID=sa;Password=1;" }, "NotificationService": { "Type": "Email" }, "NationReminderService": { "ListenAddress": "0.0.0.0", "ListenPort": 12989 }, "EmailService": { "From": "yourEmail", "FromFriendlyName": "YourServerName??", "SmtpServer": "smtp.gmail.com", "UseSSL": true, "Port": 465, "Username": "FOLLOW https://code-maze.com/aspnetcore-send-email/", "Password": "FOLLOW https://code-maze.com/aspnetcore-send-email/", "SkipTokenValidation": false }, "ServiceCompany": 11, "RequestTimeoutSeconds": 60, "PortalCGIAgentHeader": "Portal_CGI_Agent", "SaltKey": "eset5ag.nsy-g6ky5.mp", "AllowedHosts": "*" }

Quote:

Originally Posted by vasilealfredbrad Hello, I would like to better understand how safe these server files really are, especially the SRO-R server files. I already checked them myself and, from what I can see, they seem to contain fewer viruses than other releases, but it’s still not very clear what kind of risks they may pose to my system. That’s why I’d like to ask: How safe are these files in reality? What kind of damage or risks could they cause to a machine? How do other private server owners usually “clean” or secure these files? Is there a recommended way to analyze or isolate them properly? My intention is not to open a public private server. I only want to experiment with them locally and understand how they work, but ideally in a clean and safe environment. Thank you in advance. :)