# Fleet Server Error: Error - listen tcp: address https://myserver:8220: too many colons in address **URL:** \ **Category:** Endpoint Security\ **Tags:** fleet, elastic-agent\ **Created:** [April 27, 2022, 1:43pm UTC](https://discuss.elastic.co/t/fleet-server-error-error-listen-tcp-address-https-myserver-too-many-colons-in-address/303411 "2022-04-27T13:43:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![b0r1s](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/b0r1s/32/85475_2.png) [@b0r1s](https://discuss.elastic.co/u/b0r1s)\ **Post date:** [April 27, 2022, 1:43pm UTC](https://discuss.elastic.co/t/fleet-server-error-error-listen-tcp-address-https-myserver-too-many-colons-in-address/303411/1 "2022-04-27T13:43:18Z")
Hello fellows o/ I'm facing a problem to activate my Fleet Server. All my cluster is running on CentOS 7. I used rpm instalation of elastic-agent 7.15.2 and give the follow commands: On my Elasticsearch node 2 (where I'll make the fleet server): `sudo elastic-agent enroll -f --fleet-server-es=https://elasticnode2.exemple:9220 --fleet-server-service-token=90lettersandnummbers --fleet-server-policy=36something --fleet-server-es-ca=/path/to/ca.crt` The agent enrolled but de status is stucked on "Updating": ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/1/41e6752576f18ccf9a639642063052f238b517d2.png) The output for `sudo elastic-agent status` is: ```auto Status: FAILED Message: (no message) Applications: * fleet-server (FAILED) Error - listen tcp: address https://elasticnode2.exemple:8220: too many colons in address * filebeat (HEALTHY) Running * metricbeat (HEALTHY) Running ``` I've opened the ports 8220 and 443 on firewall-cmd but when I start the agent and run `netstat -tulpn` I can't see the server listening on these ports: ```auto sudo firwall-cmd --list-ports: 9220/tcp 9300/tcp 3202/tcp 8220/tcp 8220/udp 443/tcp netstat -tulpn: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp6 0 0 ::1:6789 :::* LISTEN - tcp6 0 0 10.xxx.xxx.xxx:9300 :::* LISTEN - tcp6 0 0 ::1:9300 :::* LISTEN - tcp6 0 0 ::1:25 :::* LISTEN - tcp6 0 0 10.xxx.xxx.xxx:9220 :::* LISTEN - tcp6 0 0 ::1:9220 :::* LISTEN - ``` Here is a piece of the /var/log/elastic-agent/latestlog: ```auto 2022-04-27T10:05:02.616-0300 INFO status/reporter.go:236 Elastic Agent status changed to: 'online' 2022-04-27T10:05:02.616-0300 INFO log/reporter.go:40 2022-04-27T10:05:02-03:00 - message: Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to RESTARTING: - type: 'STATE' - sub_type: 'STARTING' 2022-04-27T10:05:02.617-0300 INFO fleet/reporter.go:156 fleet reporter dropped event because threshold[10000] was reached: &{7e07bcbd-eea9-4668-b840-84c2d0aec5df STATE {13876260790614264400 49569222163401 0x55d16df49240} STARTING Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to RESTARTING: Restarting map[]} 2022-04-27T10:05:02.617-0300 INFO log/reporter.go:40 2022-04-27T10:05:02-03:00 - message: Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to STARTING: Starting - type: 'STATE' - sub_type: 'STARTING' 2022-04-27T10:05:02.617-0300 INFO log/reporter.go:40 2022-04-27T10:05:02-03:00 - message: Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to RESTARTING: Restarting - type: 'STATE' - sub_type: 'STARTING' 2022-04-27T10:05:02.618-0300 INFO fleet/reporter.go:156 fleet reporter dropped event because threshold[10000] was reached: &{7e07bcbd-eea9-4668-b840-84c2d0aec5df STATE {13876260791368871124 49569903028301 0x55d16df49240} STARTING Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to STARTING: Starting map[]} 2022-04-27T10:05:02.618-0300 INFO fleet/reporter.go:156 fleet reporter dropped event because threshold[10000] was reached: &{7e07bcbd-eea9-4668-b840-84c2d0aec5df STATE {13876260802608945464 49580405684601 0x55d16df49240} STARTING Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to RESTARTING: map[]} 2022-04-27T10:05:03.253-0300 INFO log/reporter.go:40 2022-04-27T10:05:03-03:00 - message: Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to STARTING: Starting - type: 'STATE' - sub_type: 'STARTING' 2022-04-27T10:05:03.253-0300 INFO fleet/reporter.go:156 fleet reporter dropped event because threshold[10000] was reached: &{7e07bcbd-eea9-4668-b840-84c2d0aec5df STATE {13876260802610783164 49580407522301 0x55d16df49240} STARTING Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to STARTING: Starting map[]} 2022-04-27T10:05:03.753-0300 ERROR status/reporter.go:236 Elastic Agent status changed to: 'error' 2022-04-27T10:05:03.753-0300 ERROR log/reporter.go:36 2022-04-27T10:05:03-03:00 - message: Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to FAILED: Error - listen tcp: address https://elasticnode2.exemple:8220: too many colons in address - type: 'ERROR' - sub_type: 'FAILED' 2022-04-27T10:05:03.754-0300 INFO fleet/reporter.go:156 fleet reporter dropped event because threshold[10000] was reached: &{7e07bcbd-eea9-4668-b840-84c2d0aec5df STATE {13876260802611290964 49580408029901 0x55d16df49240} STARTING Application: fleet-server--7.15.2[7e07bcbd-eea9-4668-b840-84c2d0aec5df]: State changed to RESTARTING: Restarting map[]} ``` Some prints that can help: ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/8/987cb16b5b8a4d35f947e33da544b8b68543f014.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/449e1f87de77a5039f7dea9d29a38f41d77e77a2.png) I don't know how can I get the elastic-agent works and make the server listen on 8220. I've tried on logstash server too and get the same error: ` Error - listen tcp: address https://logstash.exemple:8220: too many colons in address` I hope you can help me 🙏 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 27, 2022, 10:15pm UTC](https://discuss.elastic.co/t/fleet-server-error-error-listen-tcp-address-https-myserver-too-many-colons-in-address/303411/2 "2022-04-27T22:15:30Z")
> [@b0r1s](#): > > `https://elasticnode2.exemple:8220:` There looks like there's an extra `:` in there, as the error mentions. You don't have a typo anywhere that might be causing this? ---
**Author:** ![b0r1s](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/b0r1s/32/85475_2.png) [@b0r1s](https://discuss.elastic.co/u/b0r1s)\ **Post date:** [May 13, 2022, 1:12pm UTC](https://discuss.elastic.co/t/fleet-server-error-error-listen-tcp-address-https-myserver-too-many-colons-in-address/303411/3 "2022-05-13T13:12:36Z")
Hey @warkolm thank you for your kick answer and sorry my delay 😳 I checked the configs and don't find any typo. The `:` Is present just on log output ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 10, 2022, 1:13pm UTC](https://discuss.elastic.co/t/fleet-server-error-error-listen-tcp-address-https-myserver-too-many-colons-in-address/303411/4 "2022-06-10T13:13:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.