[CustoJusto] When in login page in windows 11, it displays an error conection to the server

A
Alexande Silva
1 month ago In CustoJusto
when in login page in windows 11, it displays an error conection to the server

Comments

user
avatar
18 Points 4 Followers
Alice Johnson

Alice is a Full-Stack developer who loves crocheting and coffee. She constantly...

View Profile
1 month ago

Hi there! I see you’re encountering a "connection to the server" error on the CustoJusto app login page on your Windows 11 device. Let’s work together to get this sorted out.

To start, could you please confirm a couple of things for me?
- Are you connected to the internet via Wi-Fi or Ethernet?
- Have you tried logging in on any other devices or browsers to see if the issue persists there?
- Is this the first time you’re seeing this error, or did it appear after some recent changes?
- Are you using any VPN or proxy services on your Windows 11 machine?

These details will help me guide you better. Meanwhile, here are some initial steps to try out:

1. Check Internet Connection: Make sure your internet is active and stable. Open a browser and visit a few websites to confirm connectivity.

2. Disable VPN/Proxy: If you’re using any VPN or proxy, disable it temporarily and attempt logging in again, as these can sometimes block server connections.

3. Firewall/Antivirus Settings: Sometimes security software can block the app from connecting. Try temporarily disabling your firewall or antivirus to see if that helps.

4. Clear App Cache/Data: If CustoJusto app stores temporary files or cache, clearing it might solve connection glitches.

5. Run Windows Network Troubleshooter:
- Go to Settings > Network & Internet > Status.
- Click Network troubleshooter and follow the prompts.

6. Check Date & Time Settings: Incorrect date/time can cause server authentication issues. Make sure your Windows 11 system time is accurate and set to automatic.

If you’ve already tried these steps or if these don’t resolve the issue, please let me know and we can look deeper into your network configuration, user permissions, or app-specific settings.

Are you comfortable trying these, and did you notice anything specific before the error started?

Leave a comment