Hi @korenevskiy, I am unclear what you mean by 'combat site', I am hoping that means development or test site because RC2 are Release Candidates and not versions that you are supposed to install on a live / production website...

I have tested RC1 and RC2 on 2 different hosting platforms and have not seen this eternal reboot that you describe.

What can you tell us about your hosting environment? or the makeup of that website?

Is it a brand new installation or one that comes from a Joomla 3 website that you upgraded step by step to Joomla 5.3.0 RC2, does it have a lot of extensions? are they all up to date? is it using Cassiopeia or a 3rdd party template and framework and if so which ones? are you using the B/C plugin? what is your PHP version, MySQL/MariaDB version etc?

Same as #44328 ?

@exlemor a combat site, in the sense that sales are conducted on it. That is, such a site is in operation. I just didn't know what to call such a site. Previously, developers called it combat, because the sales process is like a fight against a customer.
php: 8.2.17 MySQL: 8.0.41-32
it's hard to say when the site was installed. After all, I copy it from client to client. By date, the date 2019 is indicated in the extensions table. I wonder what date is indicated in the extensions (installation, extension release)
According to the dates of the materials, the Site is set in 2020

@korenevskiy never heard in 25 years of the term combat site neither has AI - perhaps that is a term used in some countries no big deal.

To be sure that I understood you correctly are you saying that this site that you installed the Release Candidate is live / production / in operation... ?

domain site:
https://мастерскаяалатырь.рф
$live_site in config:

<?php
class JConfig {
	public $host = 'localhost';
	public $lifetime = 1500;
	public $list_limit = 200;
	public $live_site = 'https://%D0%BC%D0%B0%D1%81%D1%82%D0%B5%D1%80%D1%81%D0%BA%D0%B0%D1%8F%D0%B0%D0%BB%D0%B0%D1%82%D1%8B%D1%80%D1%8C.%D1%80%D1%84';
//...
}

ERROR in file:
/media/plg_system_guidedtours/js/guidedtours.js
in function:
function startTour(obj)
in line:
5011
code:

//Javascript file guidedtours.js in 5011 line
function startTour(obj) {
//...
    if (currentUrl !== uri + obj.steps[0].url) {
      window.location.href = uri + obj.steps[0].url;
      return;
    }
//...
}

currentUrl is: https://xn--80aaaaw4ajc2bfdcki9kra8b.xn--p1ai/administrator/index.php
uri + obj.steps[0].url is: https://мастерскаяалатырь.рф/administrator/index.php
Of course, these values are different, and of course the page goes into an endless reload loop.

These 2 addresses are the same address, but in a different record format.

site "Workshop Alatyr". Manufacture of nuts and caps.
I always install websites from AkeebaBackup. Maybe it's not about him, I'm writing just in case.

P.s. engineers are similar to programmers: they make a website and then release a tank or a ship to win the hearts of customers.

@brianteeman It looks like the problem is similar #44328

Just assume, maybe at 44328, a reboot because a different address is specified in the $live_site by mistake or just an empty one. This may be as a result of migration, or as a result of the site opening on multiple domains at once. I would suggest for Joomla CMS to implement the use of the <base> tag by default. So that the site can work not only on domains, but also on domain subfolders without specifying a live site.

So that the plugin, year, module, or picture doesn't have to think about where the picture will be. In the layout of the code, it is difficult to write the path to the picture, you have to write relative paths everywhere. And because of the relativity of the path, confusion arises. Because we have different paths to the same picture. This also applies to other files of other types.

@korenevskiy Why don't you just remove the $live_site in the configuration.php, i.e. edit the file and change it to;

public $live_site = '';

That parameter shall only be used under certain special circumstances (if you are behind a proxy), mornally it should be empty like I recommend here.

P.S.: And if you absolutely want to use the $live_site variable: Why do you URL encode it? The configuration.php should be in UTF-8 format without byte order mark, so it should be possible to use https://мастерскаяалатырь.рф. Does that help?

P.S.: And if you absolutely want to use the $live_site variable: Why do you URL encode it? The configuration.php should be in UTF-8 format without byte order mark, so it should be possible to use https://мастерскаяалатырь.рф. Does that help?

You're right, changing this value to empty or to the correct encoding helps. But I wouldn't have done that initially. How could I even specify the decoded value in the value of this field?, of course I couldn't. This happened as a result of installing Joomla from an AkeebaBackup backup.
there may be an error in the AkebaBackup component.