Network Access

Connection Issues

Experiencing connectivity issues with Memex? This guide will help you troubleshoot and resolve network or firewall-related problems.

Required Connections

To function correctly, Memex needs access to several services. Ensure the following domains are accessible if you're on a restricted network:

Domain/Service	Purpose	Port	Protocol
*.memex.tech	Core service communication	443	HTTPS
*.googleapis.com	Session management	443	HTTPS
*.us-central1-memex-desktop.cloudfunctions.net	AI model access	443	HTTPS
*.memexpublic.blob.core.windows.net	Updates and announcements	443	HTTPS
*.openaipublic.blob.core.windows.net	OpenAI services	443	HTTPS
*.api.github.com	Templates resources	443	HTTPS
*.us.i.posthog.com	Telemetry	443	HTTPS
*.sentry.io	Error reporting	443	HTTPS
*.lemonsqueezy.com	Payment processing	443	HTTPS

Identifying Connectivity Issues

You may have network issues if:

• Cannot start or send messages in Memex

• Encounter error messages about connection failures

• Experience delayed responses or timeouts

Troubleshooting Steps

1. Check Internet Connection: Ensure your device is online by visiting other websites.

2. Firewall Restrictions: If behind a corporate firewall:

   • Request IT to whitelist the domains above.

   • For personal firewalls, check settings to allow Memex access.

3. Proxy Server Issues:

   • Verify proxy allows connections to required services.

4. VPN Interference:

   • Temporarily disable VPN to test connectivity.

   • Adjust VPN settings to allow traffic to necessary domains.

5. DNS Problems:

   • Use alternative DNS servers, such as 8.8.8.8 or 1.1.1.1.

   • Flush your DNS cache to update records.

Testing Your Connection

Verify network access with these steps:

1. Open a terminal or command prompt.

2. Ping the main Memex domain:

   ping memex.tech

3. Test HTTPS connection:

   curl -I https://memex.tech

4. Repeat for other required domains.

SSL Intercept Issue (proxy)

ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)

To resolve this issue:

1. Obtain the proxy's CA certificate: If SSL interception is happening, you'll need the root CA certificate used by the proxy. This is usually a .pem or .crt file.

2. Install the proxy's CA certificate:

System-wide: The preferred method is to install this CA certificate into your operating system's trusted root certificate store.

• macOS: Add it to the "System" keychain in Keychain Access and set its trust settings to "Always Trust" for SSL.

• Windows: Import it into the "Trusted Root Certification Authorities" store for the "Local Computer".

• Linux: The method varies by distribution, but often involves placing the .crt file in /usr/local/share/ca-certificates/ and running sudo update-ca-certificates.

Need More Help?

If issues persist:

1. Document network setup details (firewall, proxy, etc.)

2. Capture screenshots of error messages.

3. Contact Memex support with this information for assistance at [e-mail], or in our Discord.

Remember that network configurations vary widely between organizations. Your IT department may need to implement specific solutions for your environment.