• Issue

  • There are too many custom domain name redirects.

SKevo
Now there is an error in my place again.

嗯… 无法访问此页面

网址为https://hub.54.lt/ 的页面可能存在问题，或者已永久移动到新的网址。
在必应中搜索 hub.54.lt
ERR_FAILED

Translate:

Um… Unable to access this page

There may be a problem with the page at https://hub.54.lt/, or it has been permanently moved to the new URL.
Search hub.54.lt in Bing
ERR_FAILED

    14569 go to SSL/TLS settings and set TLS mode to “Full”, turn off proxy, link your custom domain at https://freeflarum.com again. If everything works as intended (use Incognito mode to verify it, to bypass cache), try re-enabling the proxy after a while.

        SKevo It seems that the forum can be accessed. Can you visit it?

            SKevo I tried to switch back to 145hub.freeflarum.com, but it redirected to hub.54.lt.
            Emmm, so I changed it back.

                I plan to continue to try to solve this problem in at least 7 days.

                14569 mind the browser cache - the redirect is permanent, so the browser caches it. In order to check your domain from the point of new visitors, please use a different browser, clear your browsing history (select cached files and images) or simply use incognito/private browsing, as that bypasses the cache without messing with your existing browser data.

                When I investigated it (when the domain was assumed to be linked properly from FreeFlarum’s perspective), the redirect chain was the following:

                http://hub.54.lt => https://hub.54.lt <=> https://hub.54.lt

                For some reason, the HTTPS version of the website has an infinite recursion of redirecting to itself, likely for the reasons that are described in more detail at the link I attached in my previous post. Right now, the 145hub.freeflarum.com hostname seems to function properly on my side (no redirect, forum loads at FreeFlarum’s domain, because it was unlinked).

                    Some functions in the forum can’t be used… For example, if you click the button to view and agree to the terms of service in fof terms, there is no response. I don’t know if it’s a caching problem.
                    After refreshing, it could not be solved.
                    In private browsing is not solved too.

                      14569 yes, I can access your website now

                      14569 if you mean the blue links in the login modal, I can click on them and access them fine? Have you tried visiting it in other browser, to see if that works?

                            SKevo if you mean the blue links in the login modal, I can click on them and access them fine? Have you tried visiting it in other browser, to see if that works?

                            This problem has been solved.
                            The problem to be solved now is the slow access.

                                14569 The problem to be solved now is the slow access.

                                What happens if you turn the proxy on now? If you are stuck in a redirect loop, what encryption mode do you use at Cloudflare?

                                    SKevo I changed back to the original domain name, and I think I should solve this problem after a while.

                                      4 days later

                                      The domain name can’t be bound. What’s wrong?
                                      IMG_2427.jpeg
                                      IMG_2426.jpeg

                                        14569 can you try again? It might take some time for the DNS records to propagate all over the internet.

                                            SKevo I tried again, but it still didn’t work.

                                              I tried other domain names, but it didn’t work.

                                              I tried another test forum: hubtest.freeflarum.com (deleted)
                                              I tried to bind the domain name to it, but it didn’t work too.

                                              SKevo I think this has taken effect. The IP is right, but FreeFlarum still can’t be bound.