# A fqdn instead of 'web' in the default test url, https://web:443, in acceptance.suite.yml

**URL:** <https://forum.mautic.org/t/a-fqdn-instead-of-web-in-the-default-test-url-https-web-443-in-acceptance-suite-yml/35614>\
**Category:** Ideas and Feature Requests\
**Created:** [May 3, 2025, 10:43pm UTC](https://forum.mautic.org/t/a-fqdn-instead-of-web-in-the-default-test-url-https-web-443-in-acceptance-suite-yml/35614 "2025-05-03T22:43:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dominic.mayers](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/dominic.mayers/32/13549_2.png) [@dominic.mayers](https://forum.mautic.org/u/dominic.mayers)\
**Post date:** [May 3, 2025, 10:43pm UTC](https://forum.mautic.org/t/a-fqdn-instead-of-web-in-the-default-test-url-https-web-443-in-acceptance-suite-yml/35614/1 "2025-05-03T22:43:08Z")

</div>

Any one who test locally would benefit from it, because many components such as external APIs (Google Cloud platform, etc.) requires a fully qualified domain name (fqdn). Also, it is difficult to get a signed certificate for a non fqdn. Browsers (Chrome in particular) do not accept self-signed certificate. Changing the site url at every new install is not convenient. My first idea was to replace, in the committed files, in ` acceptance.suite.yml`, the url

```auto
URL: "https://web:443"

```

by

```auto
URL: '%SITE_URL%'

```

and set the value of `SITE_URL' in the committed environment file `.env.test`:

```auto
SITE_URL=https://web:443

```

The idea of this standard approach is that these committed files contain defaults that perhaps many applications currently depend upon and the proposed modifications will not break these  
applications, because the site url is not changed. Yet, every one could then set a different value for `SITE_URL` locally in `.env.test.local`.

Unfortunately, this standard approach is not available, because the committed configuration of codeception in Mautic, i,e., `codeception.yml`, directly depends on the local file `.env.test.local`. The code even throws an exception if that local file does not exists. Because this approach does not use `.env.test`, it does not allow to set a committed value for the test site url, which every one could then change locally. At every installation, one has to change its hard coded value in ` acceptance.suite.yml`.

I understand that perhaps changing the committed hard code value of the test site URL can lead to backward compatibility breaks. Yet, unless the approach used to configure codeception is made more flexible, I suggest it, because a non fqdn domain is problematic.

---

<div class="post-metadata">

**Author:** ![dominic.mayers](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/dominic.mayers/32/13549_2.png) [@dominic.mayers](https://forum.mautic.org/u/dominic.mayers)\
**Post date:** [May 4, 2025, 1:19am UTC](https://forum.mautic.org/t/a-fqdn-instead-of-web-in-the-default-test-url-https-web-443-in-acceptance-suite-yml/35614/2 "2025-05-04T01:19:10Z")

</div>

I propose `URL: "https://localhost:443"` in `acceptance.suite.yml` instead of `URL: "https://web:443"`. It is accepted by Google Cloud console, which is otherwise very strict on the domain names. For example, I tried `mautic.test` for an oauth redirect uri and it was rejected, even though [`.test` is reserved for “local testing scenarios”](https://en.wikipedia.org/wiki/.test). It is also possible to use these [excellent readthedocs instructions](https://openssl-ca.readthedocs.io/) to create a local CA that will sign `localhost` as a subject alternative name (SAN).