State changed as code fixing the issue is committed (bf76d776)

State changed as build OD-6906 (13.1.6) is successful

Hi @robin

I've updated from v13.1.0 to v13.1.6 and I have this error message whereas it should be fixed.

I confirm that onedev is behind an nginx instance

Is this happening if connect to port 6610 directly? If not, please share your nginx installation details including OS, version, and config files.

It's a nixos config file but you can see this quite the same as regulard nginx config.

    services.nginx.virtualHosts."xxxxx.fr" = {
        extraConfig = ''
            access_log    /var/log/nginx/xxxxx.fr.access.log;
            error_log     /var/log/nginx/xxxxxx.fr.error.log error;

            client_max_body_size 1000M;
        '';
        locations."/wicket/websocket" = {
            proxyPass = "http://localhost:6610/wicket/websocket";
            proxyWebsockets = true;
        };
        locations."/~server" = {
            proxyPass = "http://localhost:6610/~server";
            proxyWebsockets = true;
        };
        locations."/" = {
            proxyPass = "http://localhost:6610/";
        };
        forceSSL = true;
        enableACME = true;
    };

Is this happening connecting to 6610 port? What is your current session timeout, and how long this messages appears after no activity?

The nginx session timeout is set to its default (60sec).

I didn't update nginx or change its configuration but only OneDev.

So I would say there is a regression from OneDev

Is this happening connecting to 6610 port? What is your current session timeout, and how long this messages appears after no activity?

I did not get enough information. For session timeout, I mean the timeout you specified in OneDev system settings.

Is this happening connecting to 6610 port

I didn't test to 6610 directly since I need to change some conf on my server.

and how long this messages appears after no activity?

Hard to say : OneDev is always loaded in a tab of my browser. I'm working on other tabs and when I come back (several minutes after), I see the error message.

I will check by always seeing that tab...

I mean the timeout you specified in OneDev system settings.

oh sorry, I didn't know there was a such setting and never changed it.

30min, and I would say that I'm seeing the error message after that time.

I don't want to be disconnected at all, just want the same behaviour I had before updating to v13.1.6

Session timeout is both for resource and secuirty reason. Nevertheless, I added an improvement request OD-2653 so that user can decide whether or not to expire the session after certain period of time.