Re: [clamav-users] ClamAV Issue - 127.0.0.1:3310 Connection refused

On 22/08/2023 20:09, Mona AlRekabi via clamav-users wrote: Kindly, find the attached file. This log file looks fine. Clamd is starting and binding to 127.0.0.1:3310. I'm still not clear what the client application is, but you say it's running on the same host as ClamAV so it should work.

Re: [clamav-users] Failed to start clamd scanner () daemon.

On 18/08/2023 05:29, Orion Poplawski via clamav-users wrote: On 7/25/23 02:54, Bhavsar Bhushan via clamav-users wrote: Hello Support Team, Recently we have install Clam AV on RHEL 8.7 server using Installing - ClamAV Documentation But

Re: [clamav-users] Unable to start clamd

On 23/08/2023 02:11, Amit Singh via clamav-users wrote: I am able to download virus definition but unable to run clamd. Can someone help? *Command Used:*docker run -it   -v clamd-vol:/var/lib/clamav --publish 3310:3310  --network host --env 'CLAMAV_NO_FRESHCLAMD=true'  

Re: [clamav-users] ClamAV Issue - 127.0.0.1:3310 Connection refused

On 22/08/2023 08:53, Mona AlRekabi via clamav-users wrote: Dear, Kindly, we installed ClamAV Antivirus on Windows Server and we face the following issue: No connection could be made because the target machine actively refused it 127.0.0.1:3310 Please, provide us

[clamav-users] Clamonacc With Remote Clamd

Hi everyone I have a scenario where I need to run Clamonacc to watch a filesystem inside a Docker container, but clamd must be outside of the container on the host. I can't find any documentation that describes that scenario, nor anything that says it's not possible but I have seen references