Hello,
im run client 3.5.1 with server 24.01
and i cannot login 
Here the log
[index] Erreur: OC\DB\Exceptions\DbalException: An exception occurred while executing a query: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘nabv_cloud.oc_login_flow_v2’ doesn’t exist at <>
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/private/DB/QueryBuilder/QueryBuilder.php line 329
OC\DB\Exceptions\DbalException::wrap(Doctrine\DBAL\Ex … {})
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/public/AppFramework/Db/QBMapper.php line 139
OC\DB\QueryBuilder\QueryBuilder->executeStatement()
- /home/clients/e84199641735e169f944769f735e3b45/cloud/core/Service/LoginFlowV2Service.php line 222
OCP\AppFramework\Db\QBMapper->insert(OC\Core\Db\LoginFlowV2 {id: null})
- /home/clients/e84199641735e169f944769f735e3b45/cloud/core/Controller/ClientFlowLoginV2Controller.php line 287
OC\Core\Service\LoginFlowV2Service->createTokens(“momonotar-PORTE … )”)
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/private/AppFramework/Http/Dispatcher.php line 225
OC\Core\Controller\ClientFlowLoginV2Controller->init()
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/private/AppFramework/Http/Dispatcher.php line 133
OC\AppFramework\Http\Dispatcher->executeController(OC\Core\Controll … {}, “init”)
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/private/AppFramework/App.php line 172
OC\AppFramework\Http\Dispatcher->dispatch(OC\Core\Controll … {}, “init”)
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/private/Route/Router.php line 298
OC\AppFramework\App::main(“OC\Core\Contr … r”, “init”, OC\AppFramework\ … {}, {_route: “core.ClientFlowLoginV2.init”})
- /home/clients/e84199641735e169f944769f735e3b45/cloud/lib/base.php line 1023
OC\Route\Router->match("/login/v2")
- /home/clients/e84199641735e169f944769f735e3b45/cloud/index.php line 36
OC::handleRequest()
POST /index.php/login/v2
from 185.31.100.19 at 2022-05-23T16:27:48+00:00
some ideas ?
I’m with infomaniak public provider & letsencrypt ssl
Talk to your provider directly.
i m talking with him but for the moment no resolution.
My question is 
Why the table oc_login_flow_v2 don’t exist ?
Please link over your developer conversation.
A quick internet search revealed a similar issue in Polls that is due to the update process:
Polls installed tables after deleting polls related oc_migration entries.
This the behavior of NC’s migration system. Delete polls related entries in the oc_migration table. NC does not execute them when the entries are still in the table.
Maybe this will help. Always make a full backup before making any changes.
It seems different table 
How can create te oc_loin_flow_v2 table again ?
Well I create the table and it’s ok
– Hôte : 10.0.20.8
– Généré le : mar. 31 mai 2022 à 08:58
– Version du serveur : 10.3.27-MariaDB-1:10.3.27+maria~stretch-log
– Version de PHP : 7.3.28-1+0~20210503.84+debian9~1.gbp6819da
SET SQL_MODE = “NO_AUTO_VALUE_ON_ZERO”;
START TRANSACTION;
SET time_zone = “+00:00”;
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /;
/!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS /;
/!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION /;
/!40101 SET NAMES utf8mb4 */;
–
–
– Structure de la table oc_login_flow_v2
CREATE TABLE oc_login_flow_v2 (
id bigint(20) UNSIGNED NOT NULL,
timestamp bigint(20) UNSIGNED NOT NULL,
started smallint(5) UNSIGNED NOT NULL DEFAULT 0,
poll_token varchar(255) COLLATE utf8_bin NOT NULL,
login_token varchar(255) COLLATE utf8_bin NOT NULL,
public_key text COLLATE utf8_bin NOT NULL,
private_key text COLLATE utf8_bin NOT NULL,
client_name varchar(255) COLLATE utf8_bin NOT NULL,
login_name varchar(255) COLLATE utf8_bin DEFAULT NULL,
server varchar(255) COLLATE utf8_bin DEFAULT NULL,
app_password varchar(1024) COLLATE utf8_bin DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
–
– Index pour les tables déchargées
–
– Index pour la table oc_login_flow_v2
ALTER TABLE oc_login_flow_v2
ADD PRIMARY KEY (id),
ADD UNIQUE KEY poll_token (poll_token),
ADD UNIQUE KEY login_token (login_token),
ADD KEY timestamp (timestamp);
–
– AUTO_INCREMENT pour les tables déchargées
–
– AUTO_INCREMENT pour la table oc_login_flow_v2
ALTER TABLE oc_login_flow_v2
MODIFY id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT /;
/!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS /;
/!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
I had a bad update process and i think lost the table…i hope no more tables 
1 Like