Sigtao is a business application used by many local authorities and public organizations. When the connection to Sigtao fails or drops repeatedly, the classic reflex is to check the internet speed or restart the workstation. In most cases, the problem does not stem from the local network, but from an intermediate link between the browser and the application server.
The most common causes of recurring disconnections on Sigtao affect three distinct layers: browser configuration, network security policies, and software compatibility after a system update. Understanding these three levels allows for targeted diagnostics instead of guesswork.
Read also : How to find accommodation on al'in?
Browser Compatibility and Sigtao Certificates After System Update
A trend reported by several local authorities since the recent updates of browsers and operating systems (upgrades to Windows 11, new versions of Edge or Chrome): Sigtao may malfunction while other internal web applications work normally. This discrepancy is confusing because it leads to dismissing the software track.
The problem often arises from certificate management. During a major browser update, the certificate store is sometimes reset or supplemented with new root authorities. If the certificate used by the Sigtao server relies on an old or intermediate trust chain, the updated browser may silently refuse the TLS connection or drop it after a few seconds.
Related reading : How to Spy on a Phone Remotely?
To help you diagnose this type of failure, you can access the Sigtao connection on Geekovision and compare the symptoms described with those you observe on your workstation.
The first useful reflex: open the browser’s developer console (F12, Security or Network tab) and check if any certificate errors or blocks of type ERR_CERT_AUTHORITY_INVALID appear during the connection attempt. If the certificate is at fault, the solution lies with the IT department, which must update the server-side certificate chain or deploy the missing root certificate on the workstations.
Enhanced Security Policies and Sigtao Session Durations
Since 2024-2025, many public IT departments have tightened their security rules. This tightening translates into three changes that directly impact the connection to Sigtao:
- Enhanced Multi-Factor Authentication (MFA): adding or modifying the MFA layer can cause reconnection loops if the authentication token expires before the end of the Sigtao application session.
- Tighter IP restrictions: some policies only allow connections from defined address ranges. A remote workstation using a VPN with a regularly changing outgoing IP will be disconnected at each rotation.
- Shortened session durations: where the session used to remain active for several hours, the timeout can now be set to just a few tens of minutes, forcing frequent reconnections in the middle of work.
These settings do not depend on the end user. The difficulty is that the error message displayed by Sigtao does not distinguish between a session timeout and a network cut. The visible symptom (blank page, return to the login screen) is identical in both cases.
To determine if the security policy is at fault, simply note the exact time of each disconnection over a day. If the cuts occur at regular intervals (every 20 or 30 minutes, for example), it is a session timeout. If they are random but correlated with an IP address change (verifiable in the VPN logs), it is the IP restriction that is blocking.
Application Connection Plan: Mapping Flows to Sigtao
When disconnections persist despite basic checks, the most reliable method is to establish an application connection plan. This document, similar to a BI connection plan used in multi-source environments, maps each link in the chain between the user workstation and the Sigtao server.
The components to identify are as follows:
- The browser and its exact version on the client workstation
- The corporate proxy (address, filtering rules applied to Sigtao domains)
- The VPN used and its outgoing configuration (static or dynamic IP)
- The SSO (Single Sign-On) that manages authentication, along with the validity duration of the token
- The LDAP or Active Directory that validates access rights
- The Sigtao application server itself, along with the deployed version
Each link can be the source of a disconnection. Without this mapping, diagnostics are done through blind elimination, testing hypotheses without logical order. With it, a technician can isolate the faulty component in a few minutes by checking the logs of each step.
A Concrete Case of Misconfigured Proxy
In some configurations, the corporate proxy applies filtering by site category. If Sigtao is hosted on a domain that is not explicitly classified as “business application” in the proxy database, the filtering may cut the connection after a variable delay, especially during the loading of heavy pages or the submission of large forms.
The verification is done by comparing the behavior of Sigtao with and without the proxy (by temporarily using a direct connection or a test proxy). If the connection is stable without the proxy, an exception for the Sigtao domain needs to be added to the filtering rules.
Confusion Between Portals and Sigtao Login Credentials
A final factor, often underestimated, generates repeated connection failures without any technical component being down. In organizations that use multiple application portals (Sigtao, My Arkevia, messaging, intranet), users frequently confuse the credentials or access URLs.
Sigtao may have several entry points depending on the deployed version (production URL, pre-production URL, old portal not disabled). Entering the old URL sometimes redirects to a functional login page but connected to an outdated server, which causes errors after authentication.
The simple workaround: add the validated production URL to the browser favorites and remove the old entries. From the IT department’s side, properly disabling old URLs prevents this issue from recurring with each version change.
Recurring disconnections on Sigtao rarely stem from a single cause. The combination of a browser update, tightened MFA, and a misconfigured proxy can produce intermittent symptoms that only a documented connection plan can untangle. Taking the time to map the flows just once saves hours of diagnostics for each subsequent incident.