R10DEV.NET HABER SİTESİ AÇILDI!R10DEV.NET HABER SİTESİ AÇILDI!

Yardım failed to request certificate vsro
Yardım
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
Hey , so i have been following your youtube video on how to make a private sro server, ive got to globle manager bit and its telling me it has failed to request certificate, anyway to solve this ?
 
BOT
Katılım
20 Ara 2025
Mesajlar
63
Tepkime puanı
13
Puanları
8
Merhaba NaughtyG,

Bu tip hata genelde servis/proses baslangicinda eksik dosya, yanlis config, yetki problemi veya port/calisan servis cakismasindan kaynaklaniyor.

  • Ilgili servis dosyasinin gercekten mevcut oldugunu ve dogru klasorden calistirildigini kontrol et.
  • Ayni paketle gelen config, DLL ve bagimli dosyalarda eksik veya bozuk kopya olup olmadigina bak.
  • Port, IP, servis adi veya process cakismasi varsa once onu temizleyip tekrar dene.
  • Windows Defender / antivirus dosyayi engelliyor veya karantinaya aliyor mu kontrol et.
  • Mumkunse ilgili exe veya servisi tek basina cmd uzerinden acip tam hata satirini log olarak al.

Istersen kullandigin paket surumunu, ilgili config dosyasini veya tam log satirini at; hangi adimda koptugunu birlikte netlestirelim.
 
Srohakan

Srohakan

vSRO DEVELOPER
Katılım
12 May 2026
Mesajlar
146
Tepkime puanı
9
Puanları
18
Yaş
26
Konum
mardin
That error usually happens when the GlobalManager can't communicate properly with the Certification server.
A few things to check:

  • Make sure Cert service is running before GlobalManager.
  • Verify the IP addresses in your .cfg files are correct (127.0.0.1 vs VPS/local IP issues are common).
  • Check if the certification port is blocked or already in use.
  • Make sure all server files are using the same machine IP/database settings.
  • If you edited the hosts file or gateway settings, double check those too.
Also look at the Certification server console/logs — it normally tells the exact reason why the certificate request failed.
 
admin
Katılım
23 Eki 2022
Mesajlar
6,557
Çözümler
11
Tepkime puanı
4,204
Puanları
113
Yaş
28
Hey, yeah I had the same issue before.
"Failed to request certificate" usually means GlobalManager can't connect to the Certification server correctly.

Things you should check:

  1. Make sure Certification server is running BEFORE GlobalManager.
    A lot of people start GlobalManager first by mistake.
  2. Open your MachineManager.cfg, SR_GlobalManager.cfg and cert config files and make sure all IPs match.
    If you're hosting locally, use:
127.0.0.1

or your actual LAN IP consistently everywhere.

  1. Check the cert port (usually 32000/15880 depending on files).
    Sometimes another process is already using it or Windows Firewall blocks it.
  2. If you edited hosts file or changed gateway IPs from the tutorial, double check them carefully.
    One wrong IP = certificate request fail instantly.
  3. Also make sure SQL services are running properly because sometimes GlobalManager throws cert errors when DB connection fails in background.
You can usually find the exact problem inside the Certification server console/logs.
Post a screenshot of:

  • Certification window
  • GlobalManager error
  • your cfg IP settings
and I can probably tell you exactly what's wrong.
send screenshot of the exact error + cert window + globalmanager window

also send:

  • SR_GlobalManager.cfg
  • MachineManager.cfg
  • cert ip/port settings
because "failed to request certificate" is usually caused by:

  • wrong ip
  • wrong cert port
  • firewall blocking connection
  • or cert server not started first
with screenshots/configs i can tell exactly what's wrong
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
Hey, yeah I had the same issue before.
"Failed to request certificate" usually means GlobalManager can't connect to the Certification server correctly.

Things you should check:

  1. Make sure Certification server is running BEFORE GlobalManager.
    A lot of people start GlobalManager first by mistake.
  2. Open your MachineManager.cfg, SR_GlobalManager.cfg and cert config files and make sure all IPs match.
    If you're hosting locally, use:
127.0.0.1

or your actual LAN IP consistently everywhere.

  1. Check the cert port (usually 32000/15880 depending on files).
    Sometimes another process is already using it or Windows Firewall blocks it.
  2. If you edited hosts file or changed gateway IPs from the tutorial, double check them carefully.
    One wrong IP = certificate request fail instantly.
  3. Also make sure SQL services are running properly because sometimes GlobalManager throws cert errors when DB connection fails in background.
You can usually find the exact problem inside the Certification server console/logs.
Post a screenshot of:

  • Certification window
  • GlobalManager error
  • your cfg IP settings
and I can probably tell you exactly what's wrong.
send screenshot of the exact error + cert window + globalmanager window

also send:

  • SR_GlobalManager.cfg
  • MachineManager.cfg
  • cert ip/port settings
because "failed to request certificate" is usually caused by:

  • wrong ip
  • wrong cert port
  • firewall blocking connection
  • or cert server not started first
with screenshots/configs i can tell exactly what's wrong
could be be because im not using my own port and im using the port from your youtube video port 15882
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
could be be because im not using my own port and im using the port from your youtube video port 15882 ?
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:53,State:0,Class:20
fail: ISRORCert.Database.SqlDbAdapter[0]
DbAdapter error
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
---> System.ComponentModel.Win32Exception (53): The network path was not found.
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen()
--- End of stack trace from previous location ---
at ISRORCert.Database.DbAdapter.GetConnectionAsync(CancellationToken cancellationToken) in /home/runner/work/ISRORCert/ISRORCert/src/ISRORCert/Database/DbAdapter.cs:line 50
at ISRORCert.Database.DbAdapter.GetDataTableAsync[T](ICollection`1 collection, String cmdText, CancellationToken cancellationToken, DbParameter[] parameters) in /home/runner/work/ISRORCert/ISRORCert/src/ISRORCert/Database/DbAdapter.cs:line 266
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:53,State:0,Class:20
crit: ISRORCert.Model.CertificationManager[0]
Failed to query certification data...
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Joymax_Bins\Cert\
 
Srohakan

Srohakan

vSRO DEVELOPER
Katılım
12 May 2026
Mesajlar
146
Tepkime puanı
9
Puanları
18
Yaş
26
Konum
mardin
im so new to this , sorry for bothering you guys
I don't think the issue is related to port 15882. Based on the logs, the real problem seems to be the SQL Server connection.

The important part is:

"Could not open a connection to SQL Server"
and
"The network path was not found"

So the Cert service cannot reach the SQL Server instance. You should check:

  • if SQL Server is running
  • if the instance/server name is correct
  • if TCP/IP is enabled
  • firewall settings
  • connection string configuration
I'm also using the port from the YouTube video, so maybe some configs need to be adjusted for your setup.
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
so after hours of trying im still getting the same thing with cert, billing now seems ok but cert is just saying the same thing, ive had all my firewall off ect, ive followed the video step by step but i just cant seem to get it working
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
Ok so the data base is connected because of the green cercle and tick , not firewall is stopping it because firewall it completely off, tcp/ip is enabled so im not getting what im doing wrong because i followed the video step by step
 
admin
Katılım
23 Eki 2022
Mesajlar
6,557
Çözümler
11
Tepkime puanı
4,204
Puanları
113
Yaş
28
Ok so the data base is connected because of the green cercle and tick , not firewall is stopping it because firewall it completely off, tcp/ip is enabled so im not getting what im doing wrong because i followed the video step by step
Bro can you send me a screenshot of where you're getting the error? I honestly didn't understand anything.
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
screen shot of cert, thats what my main problem is , i followd every step and thats what i keep getting
 

Ekli dosyalar

  • Screenshot 2026-05-15 130343.webp
    Screenshot 2026-05-15 130343.webp
    490.4 KB · Görüntüleme: 2
admin
Katılım
23 Eki 2022
Mesajlar
6,557
Çözümler
11
Tepkime puanı
4,204
Puanları
113
Yaş
28
screen shot of cert, thats what my main problem is , i followd every step and thats what i keep getting
SqlException (0x80131904): A network-related or instance-specific error occurred...
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
The network path was not found
👉 This means my application cannot connect to SQL Server. In 99% of cases, this is a config / connection issue.

🔧 Most Common Causes and Fixes

1. ❌ Wrong Server / IP / Instance

I check my connection string:
Server=...
I make sure it is correct:
If local:
Server=127.0.0.1
or
Server=.\SQLEXPRESS
If VPS:
Server=IP_ADDRESS
👉 Most common mistake: wrong instance name (SQLEXPRESS vs MSSQLSERVER)

2. ❌ SQL Server Service is Stopped

I open:
services.msc
Then check:
  • SQL Server (MSSQLSERVER) or SQLEXPRESS
👉 If it's not running, I start it.

3. ❌ TCP/IP is Disabled

I open:
SQL Server Configuration Manager
SQL Server Network Configuration
Protocols for MSSQLSERVER
Then:
👉 Enable TCP/IP
After that:
👉 Restart SQL Server

4. ❌ Firewall Blocking Connection

Especially if I'm using a VPS:
I open port:
  • 1433 TCP
In Windows Firewall:
Inbound Rules → New Rule → Port → 1433

5. ❌ Remote Connections Disabled

In SSMS:
Server Properties → Connections
✔ Enable "Allow remote connections"

6. ❌ SQL Browser Service Not Running (if using instance name)

In Services:
  • SQL Server Browser → Start

7. ❌ DB Adapter / Config Issue

In the log I notice:
DbAdapter.cs line 50 / 266
👉 That's where the connection string is set.
I double-check:
  • Username / password correct
  • Database name correct
  • Connection string valid

🔥 Quick Test (Recommended)

I run this in CMD:

sqlcmd -S 127.0.0.1 -U sa -P password

If it doesn't connect, the issue is definitely on the SQL side.

🎯 Summary

👉 My system cannot find SQL Server (network path not found)

💬 Fast Fix (Direct Solution)

I try this connection string:

Server=127.0.0.1;Database=DB_NAME;User Id=sa;Password=PASSWORD;

And I make sure:
  • SQL Server is running
  • TCP/IP is enabled
  • Port 1433 is open
 
Katılım
14 May 2026
Mesajlar
11
Tepkime puanı
1
Puanları
3
Yaş
39
Konum
england
ok so i started to try that way and i could not make an admin account on sql and i just getting an error, so i just think its going to take me along time to get use to it all, all im trying to do is host an 80 cap server from my pc to try and learn and i cant seem to get past the first bit, thankyou for your help anyway guys its always good seeing people like to help <3
 
Üst
Reklam Ver
R10dev.net'i ana ekrana ekle!

Access Restricted

Browser developer tools or unauthorized inspection detected.
Access to this site is limited to standard browser sessions for security reasons.

Protection by r10dev.net