GithubHelp home page GithubHelp logo

izer-xyz / 3cx-docker Goto Github PK

View Code? Open in Web Editor NEW
28.0 1.0 8.0 170 KB

3CX PBX Phone System docker image. [ x86_64 | ARM | v18.x ]

License: MIT License

Dockerfile 52.72% Shell 47.28%
3cx pbx docker arm x86 voip sip

3cx-docker's People

Contributors

sinegar avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar

Forkers

finnie2006 josemarq arenawebrd gillarpc mikrot tufand flaviomeyer thomaswww

3cx-docker's Issues

Persistant Volume

Hey,

i tried to install your Docker-Container with Compose and Traefik-Setup.
Inside the Dockerfile only one volume is exposed. I dont know if this is correct, but im not able to stop the container and start it again with my configured instance. A reconfigure is needed. Maybe there is a need to define a volume, which holds the configuration data.
But maybe im wrong and i use the wrong configuration. The volume voip only binds /mnt/voip inside the container.

Persistent across reboots?

Hi,

How do I keep this persistent once the 1st docker is run? additionally ports 9000-10999 also need to be exposed. Haven't been able to get this compiled with docker-compose either

Persistant Volume Pt.2 !

thanks again for such great work..

I'm a little confused though, working 'fine' BUT.. there's no definition as to where 3CX is going to save config and setting.

docker run
-d
-t
--name=3cx
--net=host
--tmpfs /tmp
--tmpfs /run
--tmpfs /run/lock
-v /sys/fs/cgroup:/sys/fs/cgroup:ro
ghcr.io/izer-xyz/3cx:latest

(I'm running on Synology host network)

cgroup is read only. So forgive my ignorance, in the setup process it fails as it seems not to be able to save settings.
Should I at least be giving a read write defined area for all this to be written to!?

I feel like this is a minor final hurdle then I can finally ditch the VM version!
You're awesome!

Screenshot 2022-09-01 at 12 46 33

Livechat audio call silent

My livechat on my website works fine, but when someone escalates it to a call both sides simply hear nothing. What steps are there to debug? Any other ports I would need to open?

Can't start the web interface on 5015

Hello while starting the container, nothing comes up...

First run. Configure instance ...
Check config tool logs in case of any issues /var/lib/3cxpbx/Data/Logs/PbxConfigTool.log
Run WebConfig on port :5015
Created symlink /etc/systemd/system/multi-user.target.wants/setup-3cx.service -> /etc/systemd/system/setup-3cx.service.
chown: invalid user: 'phonesystem:phonesystem'

At the end of the init-3cx.sh:

chown phonesystem:phonesystem /run/phonesystem

This might be related ? User not created at docker creation ?

firewall checker no audio

i just used the 3cx-docker container to use 3cx but all ports end in failure i am hosting it on an OCI arm64 server in the cloud and i've forwarded all of the ports in https://www.3cx.com/docs/ports/ except the smtp port is there anyway to fix this issue

Server error

I keep on running into the following issue when following the installation wizard.

Server error
PostInstall.SetupException: Error starting database service: postgresql at PostInstall.SetupExecutor.StartDbService() at PostInstall.SetupExecutor.ExecuteSetup(SetupSettings setupSettings, Action1 stateChanged, Action1 errorNotifier) at PbxWebConfigTool.PbxSetupService.CreatePbxInternal(SetupSettings settings)

Any idea what this could be?

Docker not started

After initial setup docker not started

Set hostname to <535aa3c1620c>.
Failed to add address 127.0.0.1 to loopback interface: Operation not permitted
Failed to add address ::1 to loopback interface: Operation not permitted
Failed to bring loopback interface up: Operation not permitted
Failed to bump AF_UNIX datagram queue length, ignoring: Read-only file system
Setting 'fs/file-max' to '9223372036854775807'.
Failed to bump fs.file-max, ignoring: Read-only file system
RLIMIT_NOFILE is already as high or higher than we need it, not bumping.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Unified cgroup hierarchy is located at /sys/fs/cgroup.
Failed to create /init.scope control group: Read-only file system
Failed to allocate manager object: Read-only file system
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

Restoring a previous backup with 3cx-docker

Finally I got the izer-xyz up-and-running. First it didn't start with the

Failed to create /init.scope control group: Read-only file system
Failed to allocate manager object: Read-only file system
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

Error message. Which I was able to correct with the following command:

docker run --detach --privileged --volume=/sys/fs/cgroup:/sys/fs/cgroup:rw --cgroupns=host ghcr.io/izer-xyz/3cx:latest

Now 3CX started and I was able to connect to the webinterface. Unfortunately I could not do a restore from a previous backup. It gives the message below:

The backup version 18.0.7.312 is newer than the PBX version 18.0.5.418. You can restore this backup only with PBX version 18.0.7.312 or newer.

Is there any way to update the 3CX from the command line, instead of building a new image?

Container starts but cannot connect to it

I appreciate this is the only docker image I found for 3cx. We use it for our weekly call-in show as a non-profit NGO.
We are using Ubuntu 20.04 server.

It was working fine for a time, but then in suddenly stopped. I tried recreating the container using the docker command you suggest, but it just would not start properly, falling into a reboot loop.

So I created it with docker-compose.yml like so:

version: '2'

services:

  voip:
    image: ghcr.io/izer-xyz/3cx:latest
    restart: unless-stopped
    security_opt:
      - apparmor:unconfined
      - seccomp:unconfined
    tty: true # get systemd to log to console
    volumes:
      - /etc/localtime:/etc/localtime:ro # set time to the host time
      - tmp:/tmp # systemd 
      - run:/run # systemd
      - lock:/run/lock # systemd
      - voip:/mnt/voip # persistent storage
      - /sys/fs/cgroup:/sys/fs/cgroup:ro #systemd
    ports:
      - "5015:5015" # setup
      - "5090:5090"
      - "5090:5090/udp"

volumes:
  voip:
  tmp:
    driver_opts:
      type: tmpfs
      device: tmpfs
  run:
    driver_opts:
      type: tmpfs
      device: tmpfs
  lock:
    driver_opts:
      type: tmpfs
      device: tmpfs

And now it starts and gets the IP from the docker bridge. However, it is not possible to connect to it on http:\hostip:5015/?v=2
All I get is "This site can’t be reached" even though the ports seem to be redirected from the host machine.

Do you have any suggestions?

Container failling to start

Hello,

I am having issues starting the container. I tried with docker run and the docker-compose.yml provided in the repo but it results in the same error.

Configure instance ...
Restore from ...
Generate default restore config /etc/3cxpbx/setupconfig.xml ...
Created symlink /etc/systemd/system/multi-user.target.wants/3cx-webconfig.service -> /etc/systemd/system/3cx-webconfig.service.

Welcome to Debian GNU/Linux 10 (buster)!

Failed to create /init.scope control group: Read-only file system
Failed to allocate manager object: Read-only file system
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

It appears cgroup is supposed to be mounted as RO. So I really don't know what this could be due to.
My distro is Arch Linux if that helps.
Let me know if you need some more info to help identify the issue.

Question

I use it in production, will u keep it up to date?

phonesystem:phonesystem

Synology DS920+ / DSM7.1

Does the system need a user 'phonesystem' I created one with R/W access to the Docker storage just in case.. stuck!
Totally loving the idea of having this in Docker instead of running a whole VM. Thanks for all the effort!

New Note

Issues with first boot 

Failed to create /init.scope control group: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

What do I do?

Can't reach on 5001

Hi

I configure docker compose as you suggest and i have done first configuration on 5015 port.

After all i see that i can't reach login or webclient on 5001 or 5000.

I try to enter in docker container and i see that services are disabled, i use this commands for test.

systemctl is-enabled 3CXIVR01.service
systemctl is-enabled 3CXPhoneSystem01.service
systemctl is-enabled 3CXMediaServer.service
systemctl is-enabled 3CXCallFlow01.service
systemctl is-enabled 3CXFirewall.service
systemctl is-enabled 3CXAudioProvider01.service
systemctl is-enabled 3CXCfgServ01.service
systemctl is-enabled 3CXEventNotificationManager.service
systemctl is-enabled 3CXSystemService01.service
systemctl is-enabled 3CXGatewayService.service
systemctl is-enabled 3CXPhoneSystemMC01.service
systemctl is-enabled 3CXQueueManager01.service
systemctl is-enabled nginx.service

next, i use this for enable services

systemctl enable 3CXIVR01.service
systemctl enable 3CXPhoneSystem01.service
systemctl enable 3CXMediaServer.service
systemctl enable 3CXCallFlow01.service
systemctl enable 3CXFirewall.service
systemctl enable 3CXAudioProvider01.service
systemctl enable 3CXCfgServ01.service
systemctl enable 3CXEventNotificationManager.service
systemctl enable 3CXSystemService01.service
systemctl enable 3CXGatewayService.service
systemctl enable 3CXPhoneSystemMC01.service
systemctl enable 3CXQueueManager01.service
systemctl enable nginx

services seems now ENABLED but the webclient is not reached again
So i try to launch this command for status

systemctl status 3CXIVR01.service
systemctl status 3CXPhoneSystem01.service
systemctl status 3CXMediaServer.service
systemctl status 3CXCallFlow01.service
systemctl status 3CXFirewall.service
systemctl status 3CXAudioProvider01.service
systemctl status 3CXCfgServ01.service
systemctl status 3CXEventNotificationManager.service
systemctl status 3CXSystemService01.service
systemctl status 3CXGatewayService.service
systemctl status 3CXPhoneSystemMC01.service
systemctl status 3CXQueueManager01.service
systemctl status nginx.service

all services gain error except nginx, as you see:

root@dockerid:/# systemctl status 3CXIVR01.service

  • 3CXIVR01.service - 3CX PhoneSystem 01 IVR Server
    Loaded: loaded (/lib/systemd/system/3CXIVR01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXPhoneSystem01.service
  • 3CXPhoneSystem01.service - 3CX PhoneSystem 01 SIP Server
    Loaded: loaded (/lib/systemd/system/3CXPhoneSystem01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXMediaServer.service
  • 3CXMediaServer.service - 3CX PhoneSystem Media Server
    Loaded: loaded (/lib/systemd/system/3CXMediaServer.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXCallFlow01.service
  • 3CXCallFlow01.service - 3CX PhoneSystem 01 CallFlow Server
    Loaded: loaded (/lib/systemd/system/3CXCallFlow01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXFirewall.service
  • 3CXFirewall.service - 3CX PhoneSystem Firewall
    Loaded: loaded (/lib/systemd/system/3CXFirewall.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXAudioProvider01.service
  • 3CXAudioProvider01.service - 3CX PhoneSystem 01 Audio Provider Server
    Loaded: loaded (/lib/systemd/system/3CXAudioProvider01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXCfgServ01.service
  • 3CXCfgServ01.service - 3CX PhoneSystem Configuration Service
    Loaded: loaded (/lib/systemd/system/3CXCfgServ01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXEventNotificationManager.service
  • 3CXEventNotificationManager.service - 3CX Event Notification Manager
    Loaded: loaded (/lib/systemd/system/3CXEventNotificationManager.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXSystemService01.service
  • 3CXSystemService01.service - 3CX PhoneSystem 01 System Server
    Loaded: loaded (/lib/systemd/system/3CXSystemService01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXGatewayService.service
  • 3CXGatewayService.service - 3CX Gateway Service
    Loaded: loaded (/lib/systemd/system/3CXGatewayService.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXPhoneSystemMC01.service
  • 3CXPhoneSystemMC01.service - 3CX PhoneSystem 01 Management Console
    Loaded: loaded (/lib/systemd/system/3CXPhoneSystemMC01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)
    root@dockerid:/# systemctl status 3CXQueueManager01.service
  • 3CXQueueManager01.service - 3CX PhoneSystem 01 Queue Manager Server
    Loaded: loaded (/lib/systemd/system/3CXQueueManager01.service; enabled; vendor preset: enabled)
    Active: inactive (dead)

so i try to start it manually by:

systemctl start 3CXIVR01.service
systemctl start 3CXPhoneSystem01.service
systemctl start 3CXMediaServer.service
systemctl start 3CXCallFlow01.service
systemctl start 3CXFirewall.service
systemctl start 3CXAudioProvider01.service
systemctl start 3CXCfgServ01.service
systemctl start 3CXEventNotificationManager.service
systemctl start 3CXSystemService01.service
systemctl start 3CXGatewayService.service
systemctl start 3CXPhoneSystemMC01.service
systemctl start 3CXQueueManager01.service
systemctl start nginx.service

but i get error on all services:

root@dockerid:/# systemctl start 3CXIVR01.service
A dependency job for 3CXIVR01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXPhoneSystem01.service
A dependency job for 3CXPhoneSystem01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXMediaServer.service
root@dockerid:/# systemctl start 3CXCallFlow01.service
A dependency job for 3CXCallFlow01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXFirewall.service
Job for 3CXFirewall.service failed because the control process exited with error code.
See "systemctl status 3CXFirewall.service" and "journalctl -xe" for details.
root@dockerid:/# systemctl start 3CXAudioProvider01.service
A dependency job for 3CXAudioProvider01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXCfgServ01.service
Job for 3CXCfgServ01.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status 3CXCfgServ01.service" and "journalctl -xe" for details.
root@dockerid:/# systemctl start 3CXEventNotificationManager.service
root@dockerid:/# systemctl start 3CXSystemService01.service
A dependency job for 3CXSystemService01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXGatewayService.service
A dependency job for 3CXGatewayService.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXPhoneSystemMC01.service
A dependency job for 3CXPhoneSystemMC01.service failed. See 'journalctl -xe' for details.
root@dockerid:/# systemctl start 3CXQueueManager01.service
A dependency job for 3CXQueueManager01.service failed. See 'journalctl -xe' for details.

This is console after 3cx server start:

test-container | First run. Configure instance ...
test-container | Check config tool logs in case of any issues /var/lib/3cxpbx/Data/Logs/PbxConfigTool.log
test-container | Run WebConfig on port :5015
test-container | Created symlink /etc/systemd/system/multi-user.target.wants/setup-3cx.service -> /etc/systemd/system/setup-3cx.service.
test-container | Start systemd
test-container |
test-container | Welcome to Debian GNU/Linux 10 (buster)!
test-container |
test-container | [ OK ] Started Dispatch Password...s to Console Directory Watch.
test-container | [ OK ] Reached target Network is Online.
test-container | [ OK ] Reached target Swap.
test-container | [ OK ] Reached target Local File Systems.
test-container | [ OK ] Reached target Slices.
test-container | [ OK ] Listening on Journal Socket (/dev/log).
test-container | [ OK ] Reached target Paths.
test-container | [ OK ] Listening on Journal Socket.
test-container | Starting Create System Users...
test-container | [ OK ] Reached target Local Encrypted Volumes.
test-container | Starting Journal Service...
test-container | [ OK ] Reached target Sockets.
test-container | [ OK ] Started Create System Users.
test-container | [ OK ] Started Journal Service.
test-container | [ OK ] Reached target System Initialization.
test-container | [ OK ] Started Daily Cleanup of Temporary Directories.
test-container | [ OK ] Reached target Timers.
test-container | [ OK ] Reached target Basic System.
test-container | Starting A high performan...and a reverse proxy server...
test-container | Starting Setup 3CX...
test-container | Starting Flush Journal to Persistent Storage...
test-container | [ OK ] Started Flush Journal to Persistent Storage.
test-container | [ OK ] Created slice system-postgresql.slice.
test-container | Starting PostgreSQL Cluster 11-main...
test-container | [ OK ] Started A high performanc...r and a reverse proxy server.
test-container | [ OK ] Started PostgreSQL Cluster 11-main.
test-container | Starting PostgreSQL RDBMS...
test-container | [ OK ] Started PostgreSQL RDBMS.
test-container | [ OK ] Started Setup 3CX.
test-container | [ OK ] Reached target Multi-User System.
test-container | [ OK ] Reached target Graphical Interface.

Where i'm wrong?

Any time I restart the container portainer log give me this

The container is on a Ubuntu 21.10 docker installation
As I wrote in the title of the issue any time I restart the container the log give me this:

Welcome to Debian GNU/Linux 10 (buster)!

[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Reached target Slices.
[  OK  ] Listening on Journal Socket.
[  OK  ] Reached target Local File Systems.
[  OK  ] Reached target Network is Online.
[  OK  ] Reached target Swap.
[  OK  ] Started Dispatch Password...s to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Created slice system-postgresql.slice.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Sockets.
         Starting Journal Service...
         Starting Create System Users...
[  OK  ] Started Create System Users.
[  OK  ] Started Journal Service.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Reached target Basic System.
         Starting 3CX Event Notification Manager...
         Starting 3CX PhoneSystem Firewall...
         Starting 3CX PhoneSystem Media Server...
         Starting PostgreSQL Cluster 11-main...
         Starting A high performan...and a reverse proxy server...
         Starting Flush Journal to Persistent Storage...
[FAILED] Failed to start 3CX PhoneSystem Firewall.
See 'systemctl status 3CXFirewall.service' for details.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started 3CX PhoneSystem Media Server.
[  OK  ] Started A high performanc...r and a reverse proxy server.
[FAILED] Failed to start 3CX Event Notification Manager.
See 'systemctl status 3CXEventNotificationManager.service' for details.
[  OK  ] Started PostgreSQL Cluster 11-main.
         Starting PostgreSQL RDBMS...
[  OK  ] Started PostgreSQL RDBMS.
         Starting 3CX PhoneSystem Configuration Service...
[  OK  ] Started 3CX PhoneSystem Configuration Service.
         Starting 3CX PhoneSystem 01 Audio Provider Server...
         Starting 3CX PhoneSystem 01 Management Console...
         Starting 3CX PhoneSystem 01 SIP Server...
         Starting 3CX PhoneSystem 01 System Server...
[  OK  ] Started 3CX PhoneSystem 01 Audio Provider Server.
[  OK  ] Started 3CX PhoneSystem 01 SIP Server.
         Starting 3CX PhoneSystem 01 CallFlow Server...
         Starting 3CX PhoneSystem 01 IVR Server...
         Starting 3CX PhoneSystem 01 Queue Manager Server...
[  OK  ] Started 3CX PhoneSystem 01 IVR Server.
[FAILED] Failed to start 3CX PhoneSystem 01 System Server.
See 'systemctl status 3CXSystemService01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 CallFlow Server.
See 'systemctl status 3CXCallFlow01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 Queue Manager Server.
See 'systemctl status 3CXQueueManager01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 Management Console.
See 'systemctl status 3CXPhoneSystemMC01.service' for details.
[DEPEND] Dependency failed for 3CX Gateway Service.
[  OK  ] Reached target Multi-User System.</log>

I don't know why. also the login page gives me this error
image
that translate to english as server error.

I also add journalctl -xe details:

-- Logs begin at Sun 2022-02-27 18:29:01 CET, end at Sun 2022-02-27 18:29:01 CET. --
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Journal started
-- Subject: The journal has been started
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The system journal process has started up, opened the journal
-- files for writing and is now ready to process requests.
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is 8.0M, max 190.3M, 182.3M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is currently using 8.0M.
-- Maximum allowed usage is set to 190.3M.
-- Leaving at least 285.5M free (of currently available 1.8G of disk space).
-- Enforced usage limit is thus 190.3M, of which 182.3M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:3:1-22: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is 8.0M, max 190.3M, 182.3M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is currently using 8.0M.
-- Maximum allowed usage is set to 190.3M.
-- Leaving at least 285.5M free (of currently available 1.8G of disk space).
-- Enforced usage limit is thus 190.3M, of which 182.3M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table inet filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:4:1-28: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain inet filter input
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:5:1-34: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain inet filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:6:1-47: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule inet filter input jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:7:1-36: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain inet filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:9:1-20: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table ip filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:10:1-26: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip filter INPUT
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:11:1-32: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:12:1-45: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule ip filter INPUT jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:13:1-34: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain ip filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:15:1-21: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table ip6 filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:16:1-27: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip6 filter INPUT
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:17:1-33: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip6 filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:18:1-46: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule ip6 filter INPUT jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:19:1-35: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain ip6 filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:21:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table inet filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:22:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:24:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:25:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:23:17-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ip daddr 224.0.1.75 counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:24:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:25:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:29:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table ip filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:30:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:32:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:33:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:31:17-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ip daddr 224.0.1.75 counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:32:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:33:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:37:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table ip6 filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:38:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:39:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:40:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:39:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:40:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nginx[31]: nginx: [warn] duplicate network "::0/0", value: "0", old value: "1" in /etc/nginx/sites-enabled/3cxpbx:14
Feb 27 18:29:01 1f83ca7dea18 postgresql@11-main[30]: Removed stale pid file.
Feb 27 18:29:01 1f83ca7dea18 nginx[68]: nginx: [warn] duplicate network "::0/0", value: "0", old value: "1" in /etc/nginx/sites-enabled/3cxpbx:14

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.