# Cannot connect to Mattermost

**URL:** <https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352>\
**Category:** Troubleshooting\
**Created:** [October 26, 2019, 4:01pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352 "2019-10-26T16:01:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![UHLHosting](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/uhlhosting/32/2264_2.png) [@UHLHosting](https://forum.mattermost.com/u/UHLHosting)\
**Post date:** [October 26, 2019, 4:01pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/1 "2019-10-26T16:01:22Z")

</div>

What happened to the pre-release instance?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/mattermost/original/2X/f/f5a1f46de89666939e79b4bb20993e02b05e1ffe.png)

---

<div class="post-metadata">

**Author:** ![amy.blais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/amy.blais/32/7481_2.png) [@amy.blais](https://forum.mattermost.com/u/amy.blais)\
**Post date:** [October 28, 2019, 12:04pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/2 "2019-10-28T12:04:56Z")

</div>

@UHLHosting Are you still experiencing this issue?

---

<div class="post-metadata">

**Author:** ![UHLHosting](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/uhlhosting/32/2264_2.png) [@UHLHosting](https://forum.mattermost.com/u/UHLHosting)\
**Post date:** [October 28, 2019, 12:25pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/3 "2019-10-28T12:25:59Z")

</div>

@amy.blais Pre-release seem to move into community found it asap as i read the new docs. Maybe a redirect from old subdomain to new one would avoid confusion.

---

<div class="post-metadata">

**Author:** ![seven-plus-t](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@seven-plus-t](https://forum.mattermost.com/u/seven-plus-t)\
**Post date:** [October 28, 2019, 1:30pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/4 "2019-10-28T13:30:18Z")

</div>

Same thing happened to me. Had the pre-release URL configured everywhere and all of a sudden it stopped working. An announcement by mail or redirect to [community.mattermost.com](http://community.mattermost.com) would be very helpful to prevent confusion. People using the old URL might have the impression the service is down.

---

<div class="post-metadata">

**Author:** ![UHLHosting](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/uhlhosting/32/2264_2.png) [@UHLHosting](https://forum.mattermost.com/u/UHLHosting)\
**Post date:** [October 28, 2019, 1:34pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/5 "2019-10-28T13:34:13Z")

</div>

Indeed this move was like made with legs and by someone running not thinking of all users that can be affected. And there is a golden rule on any subdomain in production or in place a redirection is a must. To avoid issues of any kinds.

---

<div class="post-metadata">

**Author:** ![fbartels](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/fbartels/32/3835_2.png) [@fbartels](https://forum.mattermost.com/u/fbartels)\
**Post date:** [October 28, 2019, 2:34pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/6 "2019-10-28T14:34:45Z")

</div>

and a redirect from http to https would be helpful for [https://community.mattermost.com/](https://community.mattermost.com/) as well.

---

<div class="post-metadata">

**Author:** ![amy.blais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/amy.blais/32/7481_2.png) [@amy.blais](https://forum.mattermost.com/u/amy.blais)\
**Post date:** [October 28, 2019, 4:23pm UTC](https://forum.mattermost.com/t/cannot-connect-to-mattermost/8352/7 "2019-10-28T16:23:33Z")

</div>

Hi all, I was notified that pre-release was down but it’s back up again.  
Plans for deprecating pre-release will be done at some point as well.