No data on the Dashboard

› VitalPBX Community Support › General Discussion › No data on the Dashboard

  • Post
Viewing 15 replies - 1 through 15 (of 27 total)
1 2
  • Replies
    • January 26, 2018 at 10:28 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    This happened suddenly or was not working since the installation?

    0
    • January 26, 2018 at 10:29 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    may you post the output of the following command: systemctl status vpbx-monitor.service

    0
    • January 26, 2018 at 10:36 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    ● vpbx-monitor.service – VitalPBX Server Monitoring
    Loaded: loaded (/usr/lib/systemd/system/vpbx-monitor.service; enabled; vendor preset: disabled)
    Active: active (running) since Fri 2018-01-26 15:01:17 MST; 33min ago
    Main PID: 14589 (vpbx)
    CGroup: /system.slice/vpbx-monitor.service
    └─14589 /usr/share/ombutel/monitor/vpbx

    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerEntry”,”actionid”:”1517005251836″,”channeltype”:”SIP”,”objectname”:”VI3-In”,”chanobjecttype”:”peer”,”ipaddress”:”209.166.154.70″,”ipport”:”5060″,”dynamic…
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerEntry”,”actionid”:”1517005251836″,”channeltype”:”SIP”,”objectname”:”Vitel-Inbound2″,”chanobjecttype”:”peer”,”ipaddress”:”64.2.142.90″,”ipport”:”5060″,”dy…
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerEntry”,”actionid”:”1517005251836″,”channeltype”:”SIP”,”objectname”:”Vitel-Outbound2″,”chanobjecttype”:”peer”,”ipaddress”:”64.2.142.93″,”ipport”:”5060″,”d…
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerEntry”,”actionid”:”1517005251836″,”channeltype”:”SIP”,”objectname”:”Vitel-Outbound3″,”chanobjecttype”:”peer”,”ipaddress”:”64.2.142.107″,”ipport”:”5060″,”…
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerEntry”,”actionid”:”1517005251836″,”channeltype”:”SIP”,”objectname”:”Vitel-inbound”,”chanobjecttype”:”peer”,”ipaddress”:”64.2.142.110″,”ipport”:”5060″,”dy…
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerlistComplete”,”actionid”:”1517005251836″,”eventlist”:”Complete”,”listitems”:”39″}
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”PeerlistComplete”,”actionid”:”1517005251837″,”eventlist”:”Complete”,”listitems”:”0″}
    Jan 26 15:20:51 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”CoreShowChannelsComplete”,”actionid”:”1517005251838″,”eventlist”:”Complete”,”listitems”:”0″}
    Jan 26 15:20:52 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”UserEvent”,”privilege”:”user,all”,”userevent”:”READYRELOAD”,”channel”:”ZAP/1″,”actionid”:”128″}
    Jan 26 15:20:53 vitalpbx.local vpbx[14589]: Manager Event: {“event”:”UserEvent”,”privilege”:”user,all”,”userevent”:”FOP2RELOAD”,”do”:”FOP2RELOAD”,”channel”:”ZAP/1″}
    Hint: Some lines were ellipsized, use -l to show in full.

    0
    • January 26, 2018 at 10:38 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Also, I just noticed it so I am pretty sure it was working initially then stopped

    0
    • January 26, 2018 at 10:39 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    The service is running correctly, there is no reason to don’t receive the info on Dashboard, the only reason should be that ports are blocked by firewall, however, those port are enabled by default.

    May you give us any other clue about your issue?

    0
    • January 26, 2018 at 10:49 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    I have a mikrotik firewall, are there ports I need open for this to work.

    I have temporarily disabled the VitelPBX fire wall to test and it still looks the same

    What ports should I be looking at

    0
    • January 26, 2018 at 10:51 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    I have ports 22, 80 and 443 open to my office ip address in the mikrotik

    0
    • January 26, 2018 at 10:53 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Oh I feed dumb

    I guess on this new version I need 3000 and 3005  TCP forwarded as well it works now

    Thanks

    0
    • January 26, 2018 at 10:53 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    If you are running vitalpbx over http open the port 3000, if is over https open the port 3005

    0
    • January 26, 2018 at 10:54 pm
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Got it 

    Thanks so much !!

    0
    • April 10, 2018 at 12:03 pm
    voiprehberi
    Participant
    Up
    0
    Down

    I have same problem. Dashboard status has stopped. I have 3000 and 3005 ports open on Firewall/Services but i cant see anything onn Dashboard. I am using cloudflare but just dns forward. When i enter with the server ip dashboard works but not working with A dns forward.

    One more thing how can i forward sip ports to domain ? Like sip.domain.com ?

    Thank you.

    0
    • April 10, 2018 at 1:28 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down
    Posted by: raksart

    I have same problem. Dashboard status has stopped. I have 3000 and 3005 ports open on Firewall/Services but i cant see anything onn Dashboard. I am using cloudflare but just dns forward. When i enter with the server ip dashboard works but not working with A dns forward.

    One more thing how can i forward sip ports to domain ? Like sip.domain.com ?

    Thank you.

    Check the following link: Which ports will Cloudflare work with?

    0
    • July 22, 2018 at 4:26 pm
    Pinwheel
    Participant
    Up
    0
    Down

    Experiencing the same problem. Everything is working perfectly except no data in the dashboard. Firewall is configured correctly but all 0’s on the dashboard.

    Any ideas on resolution gratefully appreciated.

    0
    • July 22, 2018 at 4:54 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    If you are using an extra firewall, like fortinet or something like that, you must to open the port also there

    0
    • July 22, 2018 at 5:39 pm
    Pinwheel
    Participant
    Up
    0
    Down

    Running on CentOS on a VPS. All other ports connections seem to work fine. netstat -a does not show 3000 or 3005 listening however. Do they need to be added separately to IP tables?

    0
Viewing 15 replies - 1 through 15 (of 27 total)
1 2
  • The forum ‘General Discussion’ is closed to new topics and replies.