# Elastic Agent 7.10 - Setup - Invalid URL - NULL

**URL:** <https://discuss.elastic.co/t/elastic-agent-7-10-setup-invalid-url-null/255416>\
**Category:** Kibana\
**Tags:** docker, fleet\
**Created:** [November 14, 2020, 7:55pm UTC](https://discuss.elastic.co/t/elastic-agent-7-10-setup-invalid-url-null/255416 "2020-11-14T19:55:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![casa0](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@casa0](https://discuss.elastic.co/u/casa0)\
**Post date:** [November 14, 2020, 7:55pm UTC](https://discuss.elastic.co/t/elastic-agent-7-10-setup-invalid-url-null/255416/1 "2020-11-14T19:55:17Z")

</div>

Hi, I'm seeing an error "Invalid URL: null" when trying to view any pages related to fleet.

I was testing 7.9.3 in Docker and was able to add a few agents, then upgraded to 7.10.0. Now none of the fleet pages will load. Everything else seems to work though. I can add agents by using the old config scripts in "standalone" mode, but managing any of the Elastic Agents through fleet is not working.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/5/e507a54cb319433459afaba62bd4179a121e5ca7.png)

`docker-compose logs` Stack Trace:

```auto
kib01 | 
{"type":"log",
"@timestamp":"2020-11-14T19:19:08Z",
"tags ["error","plugins","ingestManager"],
"pid":6,
"message":"{ TypeError [ERR_INVALID_URL]: Invalid URL: null
   at onParseError (internal/url.js:241:17)
   at new URL (internal/url.js:319:5)
   at getFullAgentPolicyKibanaConfig (/usr/share/kibana/x-pack/plugins/ingest_manager/common/services/full_agent_policy_kibana_config.js:15:26)
   at AgentPolicyService.getFullAgentPolicy (/usr/share/kibana/x-pack/plugins/ingest_manager/server/services/agent_policy.js:505:85)
   at process._tickCallback (internal/process/next_tick.js:68:7) input: 'null' }"}

```

Any thoughts on what might be happening?

I'm hoping it's possible to fix this in place and retain the current data for a bit even though it's a test environment since I actually found some interesting indicators of compromise.

Cheers

---

<div class="post-metadata">

**Author:** ![nchaulet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nchaulet/32/77896_2.png) [@nchaulet](https://discuss.elastic.co/u/nchaulet)\
**Post date:** [November 17, 2020, 4:43pm UTC](https://discuss.elastic.co/t/elastic-agent-7-10-setup-invalid-url-null/255416/2 "2020-11-17T16:43:17Z")

</div>

Hi Chris

Thanks for testing Elastic Agent 🙂

Looks like the Fleet settings are invalid, not sure how it happened, but you can probably try to fix it by removing the settings with the following (and reconfiguring them after)

You can run this as a superuser to delete the settings, they will be recreated after you visit the settings tab in Fleet

```
POST .kibana/_delete_by_query
{
  "query": {
    "bool": {
      "must": [
        {
          "terms": {
            "type": [
              "ingest_manager_settings"
            ]
          }
        }
      ]
    }
  }
}

```

Let me know if it fix your problem

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 15, 2020, 4:43pm UTC](https://discuss.elastic.co/t/elastic-agent-7-10-setup-invalid-url-null/255416/3 "2020-12-15T16:43:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.