Hello Korost,

in OTOBO 10.1 there are a couple of new OTOBO SysConfig settings that control the behaviour. In your case I can imagine that the customer interface is deactivated and that the agent interface is configured as the default. Could you check your setup. In my test installation it looks like this:

bes:~/devel/OTOBO/otobo (rel-10_1)$ bin/otobo.Console.pl Admin::Config::Read --setting-name CustomerFrontend::Active
Gathering setting value...

Setting: CustomerFrontend::Active
1

Done.
bes:~/devel/OTOBO/otobo (rel-10_1)$ bin/otobo.Console.pl Admin::Config::Read --setting-name Frontend::DefaultInterface
Gathering setting value...

Setting: Frontend::DefaultInterface
index.pl

Done.
bes:~/devel/OTOBO/otobo (rel-10_1)$

If the customer frontend is deactivated you could activate it via the SysConfig in the Web-GUI or with the command:

bin/otobo.Console.pl Admin::Config::Update –setting-name CustomerFrontend::Active –value 1

Best regards,

Bernhard

In order to avoid this effect the updating instructions have been updated in https://doc.otobo.org/manual/installation/10.1/de/content/updating.html . Step 4 now includes the command

/opt/otobo/bin/otobo.Console.pl Maint::Config::Rebuild

which should make the upgrading procedure smoother.