Skip to content

Unable to connect to the server.Please check your network connection #5096

Closed as not planned

Description

@reader1000er12

Platform

Desktop - Windows

Describe the bug

Folo-1.14.0-windows-x64
windows11
Unable to connect to the server.Please check your network connection

Image #5090

Entry ID

No response

Relevant Information

No response

Reproduction Video

No response

Environment

No response

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • This issue is valid

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

Activity

  1. pixeldin commented on Sep 26, 2026

    @pixeldin

    Still with this problem,any update?🥺

  2. DIYgod commented on Sep 26, 2026

    @DIYgod
    Member

    This is a network issue in some regions: the Folo API can't be reached from your network, so it needs to be resolved on your side (for example with a proxy; on desktop you can set one under Settings → General → Proxy). Closing.

  3. pixeldin commented on Sep 27, 2026

    @pixeldin

    OK, I just adding this in my proxy rule:

    domain:folo.is
    domain:follow.is
    
  4. reader1000er12 commented on Sep 29, 2026

    @reader1000er12
    Author
  5. reader1000er12 commented on Sep 29, 2026

    @reader1000er12
    Author
  6. reader1000er12 commented on Sep 29, 2026

    @reader1000er12
    Author
  7. DIYgod commented on Nov 5, 2026

    @DIYgod
    Member

    Thanks for the follow-up. The proxy field used to silently drop values without a scheme (like 127.0.0.1:7890), which is why it looked like it couldn't be saved. This was fixed in 1.16.0: the field now saves on blur or Enter, treats host:port as an HTTP proxy, and shows an error if the value is rejected. Please update to the latest version (1.17.0) and let us know if it still happens.

  8. reader1000er12 commented on Nov 9, 2026

    @reader1000er12
    Author
  9. DIYgod commented on Nov 9, 2026

    @DIYgod
    Member

    Folo doesn't have a built-in proxy, so there's no address we can give you. Use the proxy address you set up in ProxyBridge (e.g. 127.0.0.1:7890): enter it under Settings → General → Proxy and press Enter, or check that ProxyBridge has a rule covering Folo. If it still can't connect, tell us which Folo version you're on and send screenshots of the proxy field and your ProxyBridge rule.

  10. reader1000er12 commented on Nov 11, 2026

    @reader1000er12
    Author
  11. DIYgod commented on Nov 11, 2026

    @DIYgod
    Member

    Glad you got it working. We don't block anything on our side. Whether the Folo API is reachable depends on your network, and some networks in China can't reach it directly, so on those you'll need a proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions