[GH-ISSUE #4749] [Bug]: Curl error=Problem with the SSL CA cert (path? access rights?) #2945

New issue

Closed

opened 2026-02-27 03:06:27 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:06:27 +03:00

Owner

Originally created by @t3mpesta on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4749

User story

unable to publish new server

Game

Arma Reforger

Linux distro

RedHat 9

Command

command: start

Further information

on start, the gameserver is unable to comunicate with steam and/or arma server during server publish.

obvious http request works fine on system.
no problem using a docker rhel 9 image and a steamcmd installation in a new container.

server error log:

BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?)
BACKEND (E): Http Error (BAD_REQUEST)
BACKEND (E): [RestApi] ID:[4] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request

Relevant log output

NETWORK      : RPL listen address requested: '0.0.0.0:2001'
NETWORK      : Starting RPL server, listening on address 0.0.0.0:2001, fastValidation=true
DEFAULT      : BattlEye Server: Loading BattlEye library from path '/home/armarserver/serverfiles/battleye/BEServer_x64.so'.
DEFAULT      : BattlEye Server: 'Initialized (v1.220, Arma Reforger 1.2.1.173)'
DEFAULT      : BattlEye Server: Initialized.
'EFAULT      : BattlEye Server: 'Config entry: GameID armar
DEFAULT      : BattlEye Server: 'Config entry: MasterPort 2001'
BACKEND   (E): Curl error=Problem with the SSL CA cert (path? access rights?)
BACKEND   (E): Http Error (BAD_REQUEST)
BACKEND   (E): [RestApi] ID:[1] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request
BACKEND   (E): Curl error=Problem with the SSL CA cert (path? access rights?)
BACKEND   (E): Http Error (BAD_REQUEST)
BACKEND   (E): [RestApi] ID:[2] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request
BACKEND   (E): Curl error=Problem with the SSL CA cert (path? access rights?)
BACKEND   (E): Http Error (BAD_REQUEST)
BACKEND   (E): [RestApi] ID:[3] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request
BACKEND   (E): Curl error=Problem with the SSL CA cert (path? access rights?)
BACKEND   (E): Http Error (BAD_REQUEST)
BACKEND   (E): [RestApi] ID:[4] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request
DEFAULT      : BattlEye Server: Done.
RPL          : IReplication:: Finishing...
RPL          : rpl::Pip::ProcessNetToGame
 RPL          : IReplication: Finished
RPL          : Pip::Destroy
ENGINE    (E): Unable to initialize the game
ENGINE       : Game destroyed.
RPL          : Pip::Destroy

Steps to reproduce

No response

Originally created by @t3mpesta on GitHub (Jan 16, 2025). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4749 ### User story unable to publish new server ### Game Arma Reforger ### Linux distro RedHat 9 ### Command command: start ### Further information on start, the gameserver is unable to comunicate with steam and/or arma server during server publish. obvious http request works fine on system. no problem using a docker rhel 9 image and a steamcmd installation in a new container. server error log: BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?) BACKEND (E): Http Error (BAD_REQUEST) BACKEND (E): [RestApi] ID:[4] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request ### Relevant log output ```shell NETWORK : RPL listen address requested: '0.0.0.0:2001' NETWORK : Starting RPL server, listening on address 0.0.0.0:2001, fastValidation=true DEFAULT : BattlEye Server: Loading BattlEye library from path '/home/armarserver/serverfiles/battleye/BEServer_x64.so'. DEFAULT : BattlEye Server: 'Initialized (v1.220, Arma Reforger 1.2.1.173)' DEFAULT : BattlEye Server: Initialized. 'EFAULT : BattlEye Server: 'Config entry: GameID armar DEFAULT : BattlEye Server: 'Config entry: MasterPort 2001' BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?) BACKEND (E): Http Error (BAD_REQUEST) BACKEND (E): [RestApi] ID:[1] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?) BACKEND (E): Http Error (BAD_REQUEST) BACKEND (E): [RestApi] ID:[2] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?) BACKEND (E): Http Error (BAD_REQUEST) BACKEND (E): [RestApi] ID:[3] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request BACKEND (E): Curl error=Problem with the SSL CA cert (path? access rights?) BACKEND (E): Http Error (BAD_REQUEST) BACKEND (E): [RestApi] ID:[4] TYPE:[EBREQ_GAMECONFIG_List] Error - Cannot send request DEFAULT : BattlEye Server: Done. RPL : IReplication:: Finishing... RPL : rpl::Pip::ProcessNetToGame RPL : IReplication: Finished RPL : Pip::Destroy ENGINE (E): Unable to initialize the game ENGINE : Game destroyed. RPL : Pip::Destroy ``` ### Steps to reproduce _No response_

kerem

2026-02-27 03:06:27 +03:00

closed this issue
added the
type: bug

info: steamcmd

command: install

info: docker

command: start
labels

kerem commented

2026-02-27 03:06:28 +03:00

Author

Owner

@t3mpesta commented on GitHub (Jan 16, 2025):

solved added a link :
sudo ln -s /etc/pki/tls/certs/ca-bundle.crt /etc/ssl/certs/ca-certificates.crt

seems a problem that affect plain rhel distro.

@t3mpesta commented on GitHub (Jan 16, 2025): solved added a link : sudo ln -s /etc/pki/tls/certs/ca-bundle.crt /etc/ssl/certs/ca-certificates.crt seems a problem that affect plain rhel distro.

kerem commented

2026-02-27 03:06:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 19, 2026):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Jan 19, 2026): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:56:03 +03:00

[PR #2960] [MERGED] fix(update): allow steamcmd to check for update on beta branches #3853