<p>On a multi-site setup, you need to use the multi-site array syntax for the <code>siteUrl</code> config setting like so:</p>

<pre><code>'siteUrl' =&gt; [
    'siteHandle1' =&gt; 'https://foo.com/',
    'siteHandle2' =&gt; 'https://bar.com/',
],
</code></pre>

CC BY-SA 3.0
2018-01-01T00:06:33.907Z
In my testing it appears that the `siteUrl` array in `general.php` does not override the `Sites->Base URL` setting that is stored in the db. If I set an array of `siteUrl`s in my general.php and then set incorrect values as my Base URLs in the Sites settings, the incorrect values continue to throw errors. Maybe the siteUrl setting gets respected in other places but it appears that the Debug Toolbar in the CP prioritizes the Base URL values in the db.
Ben Parizek
CC BY-SA 4.0
2017-12-31T23:22:05.080Z
2018-11-02T18:44:26.270Z
2018-11-02T18:44:26.270Z
Brad Bell
<p>I've enabled <code>Show the debug toolbar on the Control Panel</code> in my Craft Admin account in a local development environment that uses SSL. As soon as I enable it, I get the following error each time I load any page in the CP:</p>

<pre><code>VM1685:1 Mixed Content: The page at 'https://domain.dev/admin/myaccount' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://craft3.dev/actions/debug/default/toolbar?tag=5a495cbcf3e15'. This request has been blocked; the content must be served over HTTPS.
</code></pre>

<p>SSL seems to be set up and working fine. I have the <code>siteUrl</code> variable in my <code>general.php</code> set up with an <code>https</code> url as well:</p>

<pre><code>'siteUrl' =&gt; 'https://domain.dev',
</code></pre>

<p>What could be triggering this warning?</p>

CC BY-SA 3.0
2017-12-31T22:53:37.003Z
Just tested locally and not able to reproduce.  Do you have a multi-site setup by chance?
Brad Bell
CC BY-SA 3.0
2017-12-31T23:07:30.027Z
Yes, I have several Sites. And, it looks like that's the issue. Updating the siteUrl setting fixes the error. Do you folks have any docs yet on what can be overridden in the `general.php` file? It looks like Sites stores the URL in the database.
Ben Parizek
<control-panel><debugging>
Yii Toolbar triggering mixed content warning in CP
# Yii Toolbar triggering mixed content warning in CP

(Asked by: username_0 on 2017-12-31)

I've enabled Show the debug toolbar on the Control Panel in my Craft Admin account in a local development environment that uses SSL. As soon as I enable it, I get the following error each time I load any page in the CP:
VM1685:1 Mixed Content: The page at 'https://domain.dev/admin/myaccount' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://craft3.dev/actions/debug/default/toolbar?tag=5a495cbcf3e15'. This request has been blocked; the content must be served over HTTPS.

SSL seems to be set up and working fine. I have the siteUrl variable in my general.php set up with an https url as well:
'siteUrl' => 'https://domain.dev',

What could be triggering this warning?

**Tags:** control-panel, debugging

> **Comments:**
> **username_1**: Just tested locally and not able to reproduce.  Do you have a multi-site setup by chance?  
> **username_0**: Yes, I have several Sites. And, it looks like that's the issue. Updating the siteUrl setting fixes the error. Do you folks have any docs yet on what can be overridden in the `general.php` file? It looks like Sites stores the URL in the database.  

---

## 1 answers

### Answer by username_1 on 2017-12-31. Score: 1

On a multi-site setup, you need to use the multi-site array syntax for the siteUrl config setting like so:
'siteUrl' => [
    'siteHandle1' => 'https://foo.com/',
    'siteHandle2' => 'https://bar.com/',
],

> **Comments:**
> **username_0**: In my testing it appears that the `siteUrl` array in `general.php` does not override the `Sites->Base URL` setting that is stored in the db. If I set an array of `siteUrl`s in my general.php and then set incorrect values as my Base URLs in the Sites settings, the incorrect values continue to throw errors. Maybe the siteUrl setting gets respected in other places but it appears that the Debug Toolbar in the CP prioritizes the Base URL values in the db.  

---

