Scheduled reports - Cannot connect to web service: couldn't connect to server

[pawel.zimny]

I recently upgraded Zabbix to 5.4.1 and I wanted to start using scheduled report, but I've got some problems with conifguration (error

Cannot connect to web service: couldn't connect to server

).

My Zabbix is running in Docker on Debian Buster. Everything is based on official containers: Zabbix Server (PostgreSQL), Zabbix Frontend (Apache, PostreSQL) and PostgreSQL12.

According do documentation (https://www.zabbix.com/documentation...ll/web_service) I installed Google Chrome browser:

• wget https://dl.google.com/linux/direct/g...rent_amd64.deb
• sudo apt install ./google-chrome-stable_current_amd64.deb

and Zabbix Web Service

• wget https://repo.zabbix.com/zabbix/5.4/d...bian10_all.deb
• dpkg -i zabbix-release_5.4-1+debian10_all.deb
• apt install zabbix-web-service

I eddited zabbix_web_service.conf:

AllowedIP=127.0.0.1,::1,0.0.0.0/0,zabbix

I edited zabbix_server.conf:

StartReportWriters=1
WebServiceURL=http://localhost:10053/report

I eddited settings in Zabbix Frontend - Administration -> General -> Other

Frontend URL: http://localhost:8085 (frontend is available at port 8085)

But when I try to test report generating i get error:
Cannot connect to web service: couldn't connect to server

I've already tried with other Frontend URLs, but nothings seems to work. I tried with: http://localhost:10053/report http://192.168.10.18:8085/ http://192.168.10.18:10053/report

I've verified that I get answear from http://192.168.10.18:10053/report :

{"detail":"Method is not supported."}

What else can I check/try?

[dmwcode]

Curious if you ever resolved this issue?

[pawel.zimny]

Curious if you ever resolved this issue?

I still have the same issue :/

[tim.mooney]

I'm not running a new enough version of Zabbix right now to test the web service, but my understanding is that it runs as a separate service, and the main Zabbix server communicates with that service.

When you installed the zabbix-web-service package, did it come with its own systemd service file? If it did, have you tried enabling and starting that service?

If it didn't come with its own systemd service file, then that probably means that the zabbix_serverd is supposed to start it. Again, I'm not sure because I'm not running that Zabbix version yet. But if zabbix_serverd is supposed to start it, have you tried restarting zabbix_serverd after you modified zabbix_serverd.conf and made the changes via the web interface?

I think the systemd service file is the more likely situation, but it's probably one or the other of those two possibilities.

[um3n]

I wonder if there is a service listening on your machine. Could you check

ss -tulpen

.
If zabbix starts correctly your reports service should listen on a port, right?

[dmwcode]

In my case I eventually got this working but I am not sure what fixed it. My server ended up crashing because the drive filled up due to a very large server log file. Once I fixed that and restarted the scheduled reports started to work. I think those problems were not related though.

[Spectator]

I have the same problem

This is the link to my Zabbix WEB interface:

http://192.168.1.1/zabbix

I've done the following so far:
apt-get install zabbix-web-service chromium
In zabbix_server.conf:
StartReportWriters = 1
WebServiceURL = http: // localhost: 10053 / report

On the WEB interface:
Administration -> General -> Other
Frontend URL: http://192.168.1.1/zabbix

At the bottom of Reports -> Scheduled reports -> Customreport (which contains its own dashboard called Customdash), the "Test" button gives this message after 1-2 minutes:

"Report generating test failed.
Cannot connect to web service: timeout was reached"

The Customdash dashboard is loaded at this link:

http://192.168.1.1/zabbix/zabbix.php?action=dashboard.print&dashboardid=60

In /var/log/zabbix/zabbix_web_service.log I only see this:
021/11/07 09: 22: 00.804623 received report request from 127.0.0.1:54190

Do you have any ideas what I could look at?

[pawel.zimny]

I found the problem.
In server configuration I was usinng address http://localhost:10053/report it was wrong because in my case Zabbix server is running in docker and Zabbix web service is not running in docker. Zabbix server wasn't albe to connect to web servcie because it was in the other network. I changed the configuration and now everything works fine. Reports are beeing generated and send

[hamimi]

HI, I currently installed Zabbix 6.0 on Ubuntu 18.04, I get an error:
Report Generating failed

• Cannot connect to web service: couldn't connect to server

Although I have enabled StartReportWriters=1 and also added
WebServiceURL=http://localhost:10053/report
also installed chromium,

What else can it be?

[Tuor]

Hi

I got the same error message: Cannot connect to web service: couldn't connect to server

Google Chrome is installed (on Ubuntu Chromium is install as snap and that is not supported by Zabbix).

Configuration:
StartReportWriters=1
WebServiceURL=http://localhost:10053/report

pgrep -af report
2098 /usr/sbin/zabbix_server: report manager #1 [jobs created 0, processed 0, idle 5.004998 sec during 5.005043 sec]
2099 /usr/sbin/zabbix_server: report writer #1 [reports started 0, sent 0, finished 0, idle 167.829255 sec during 167.829485 sec]

There is no process listening on port 10053.

It seems there is no systemd unit shipped with the package, see docs https://www.zabbix.com/documentation...ll/web_service :

After the installation, run zabbix_web_service on the machine, where the web service is installed:
shell> zabbix_web_service

temporary workaround in a screen/tmux session:
su -s /bin/sh - zabbix
zabbix_web_service -c /etc/zabbix/zabbix_web_service.conf

[hamimi]

I think my problem is, The latest Zabbix 6.0 LTS does not come standard with zabbix-web-service , even if I try install using apt install zabbix-web-service. its not found.

[Tuor]

https://repo.zabbix.com/zabbix/6.0/ubuntu/pool/main/z/zabbix/zabbix-web-service_6.0.3-1%2Bubuntu20.04_amd64.deb

[hamimi]

Thanks SO much Tuor , that worked like a charm!

[Tuor]

This doesn't solve the problem, but it is a workaround. If you reboot the server, you will have to start your screen session again. In my opinion this zabbix_web_service deserves a systemd service unit or this is maybe just a bug.

[Atsushi]

If it is a package for RHEL, it can be managed by systemd with the service name zabbix-web-service.

[Tuor]

I created a bug report: https://support.zabbix.com/browse/ZBX-20897

[Tuor]

Oh no! There is a service for it, but the service is disabled by default (or I don't know why it was disabled on my system). There is no need for any workarounds!
If you want to enable your zabbix_web_service, just run this (on distributions using systemd):

systemctl enable --now zabbix-web-service.service

The documentation should mention, that this service is disabled by default (as it seems) and you have to enable it first. Maybe other people can check, if this service is enabled or disabled on there system. Maybe it is just me being stupid.^^

[gopkris2000]

In my case, this is the problem. I have restarted the services to fix it.
# systemctl start zabbix-web-service.service

[cyber]

I think most of newly installed services are disabled by default... I guess there is no reason to start things up, if you have not yet configured it properly.

[Tuor]

Fair point.