# Meet Flint 2 (GL-MT6000 )

**URL:** <https://forum.gl-inet.com/t/meet-flint-2-gl-mt6000/31654>\
**Category:** Router\
**Created:** [July 22, 2023, 5:43am UTC](https://forum.gl-inet.com/t/meet-flint-2-gl-mt6000/31654 "2023-07-22T05:43:33Z")\
**Posts on this page:** 1\
**Showing post:** 560

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [December 28, 2023, 11:24pm UTC](https://forum.gl-inet.com/t/meet-flint-2-gl-mt6000/31654/560 "2023-12-28T23:24:51Z")

</div>

Pretty sure this is a mistake.

The screenshot tells me that @tcp is using the HTTP-challenge, which should work on every OpenWrt (at least if nobody removed the firewall itself).

@tcp You might want to have a look into the ACME script I wrote: [Is there a way to get a letsencrypt certificate for the factory DDNS on the MT6000? - #4 by admon](https://forum.gl-inet.com/t/is-there-a-way-to-get-a-letsencrypt-certificate-for-the-factory-ddns-on-the-mt6000/36541/4) - Maybe just for understanding the commands and requirements.

---

_[View the full topic](https://forum.gl-inet.com/t/meet-flint-2-gl-mt6000/31654)._