Re: kamailio tls module not loading

Hi there,

A few quick questions just to rule out the simple stuff.

- I don't see it, but I assume you have added "loadmodule "tls.so"" to the
cfg?
- In the file: /etc/kamailio/modules/tls.cfg - this points to the path
where the certs are - is that path accessible by the kamailio process for
read access? (0600 with owner kamailio or 644 with owner root etc)
- Correctly named path and cert name as well in the above file?

Hope this helps.

John.

On Mon, 16 Jun 2025 at 10:30, Timothy Delin via sr-users <
[email protected]> wrote:

> Hi everyone,
>
> I am facing an issue where I cannot load the TLS module in my Kamailio
> server. I keep receiving this error message
>
> *"0(1) ERROR: <core> [core/sr_module.c:529]: ksr_locate_module(): could
> not find module <tls> in </usr/local/lib64/kamailio/modules>*
> * 0(1) CRITICAL: <core> [core/cfg.y:4015]: yyerror_at(): parse error in
> config file /etc/kamailio/modules/tls.cfg, line 1, column 12-19: failed to
> load module"*
>
> The Kamailio that I run has this configuration
>
> version: kamailio 5.8.6 (x86_64/linux) 6c71d5
> flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE,
> Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX,
> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
> USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
> ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144,
> MAX_SEND_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT
> PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 6c71d5
> compiled on 04:12:34 Jun  6 2025 with gcc 12.2.1
> -------------------------------------------------------------------
> #global.cfg
> debug=2
> log_stderror=no
>
> memdbg=5
> memlog=5
>
> log_facility=LOG_LOCAL0
> log_prefix="{$mt $hdr(CSeq) $ci} "
>
> /* number of SIP routing processes */
> children=2
>
> /* Defining interfaces */
> #!substdef "!PUBLICIP!$env(PUBLICIP)!"
> #!substdef "!UDPPORT!$env(UDPPORT)!"
> #!substdef "!PUBLIC_UDP_SOCKET!udp:PUBLICIP:UDPPORT!"
> /* Need for TLS Support */
> #!substdef "!PUBLIC_TLS_SOCKET!TLS:PUBLICIP:5061!"
>
> #!substdef "!COREIP!$env(COREIP)!"
> #!substdef "!UDPPORT!$env(UDPPORT)!"
> #!substdef "!CORE_UDP_SOCKET!udp:COREIP:UDPPORT!"
> #!substdefs "!CORESUBNET!$env(CORESUBNET)!"
> /* listen addresses */
> listen=PUBLIC_UDP_SOCKET
> listen=CORE_UDP_SOCKET
>
> /* Need for TLS Support */
> listen=tls:0.0.0.0:5061
>
> #!substdef "!DBUSERNAME!$env(DBUSERNAME)!"
> #!substdef "!DBPASSWORD!$env(DBPASSWORD)!"
> #!substdef "!DBHOST!$env(DBHOST)!"
> #!substdef "!DBNAME!$env(DBNAME)!"
>
> #!define DBURL "mysql://DBUSERNAME:DBPASSWORD@DBHOST/DBNAME"
> #!define HTTP_API_ROUTING_ENDPOINT "http://172.16.254.30:5000/api/routing"
> ----------------------------------------------------------------
> #kamailio.cfg
>
> ####### Enable TLS  ########
> enable_tls=yes
>
> ####### Core Modules Section ########
> include_file "/etc/kamailio/modules-core.cfg"
>
> ####### Global Parameters #########
> include_file "/etc/kamailio/globals.cfg"
>
> ####### Other Modules Section ########
> include_file "/etc/kamailio/modules.cfg"
>
> ####### Custom Parameters #########
>
> /* These parameters can be modified runtime via RPC interface
>  * - see the documentation of 'cfg_rpc' module.
>  *
>  * Format: group.id = value 'desc' description
>  * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */
>
> ####### Routing Logic ########
> include_file "/etc/kamailio/routes.cfg"
>
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions --
> [email protected]
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
>

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!