What I’m trying to do
I am trying to connect my corporate computer to Obsidian Sync.
Time ago, I started this thread: Obsidian Sync: Error Unable to connect to server
Later, I found this other one: Request to add http socks proxy as built-in feature - #4 by skywind3000
Related to this post: electron/docs/api/command-line-switches.md at main · electron/electron · GitHub
The issue I am having is:
- When I start the app using no proxy on the CLI, for example the plugin Plugin Update Checker does work. But Obsidian Sync does not work. I am never able to connect to the server.
- When I start the app using a proxy on the CLI, everything works. But I also need to turn on my VPN.
- When I use the proxy, without the VPN: Obsidian Sync does not work; but
Plugin Update Checker
, Browse for Community plugins, Check for Obsidian updates: does work.
The CLI I am using is the following:
C:\Users\xxxx\AppData\Local\Programs\obsidian\Obsidian.exe --proxy-server=http://127.0.0.1:1234
When not using VPN, I am able to ping sync-13.obsidian.md
, releases.obsidian.md
and api.obsidian.md
.
When using the VPN, I am also able to ping the previous domains.
All from the Windows Terminal (cmd.exe
).
This is my system log:
SYSTEM INFO:
Obsidian version: v1.6.3
Installer version: v1.6.3
Operating system: Windows 10 Enterprise 10.0.19045
Login status: logged in
Catalyst license: insider
Insider build toggle: on
SYNC INFO:
Vault ID: xxxxxx
Host server: wss://sync-13.obsidian.md
Device name:
Allowed file types: image, audio, pdf, video, unsupported
Allowed special types: app, appearance, appearance-data, hotkey, core-plugin, core-plugin-data, community-plugin, community-plugin-data
Ignored directories:
- .obsidian/plugins/text-extractor/cache
Vault path: C:\Users\xxxxxxxxx\xxxx\Obsidian\Vault
Sync logs:
2537 Info Connecting to server
2342 Info Connection successful. Detecting changes...
....
1806 Info Fully synced
My questions
- Why am I having inconsistent behavior between the plugins and Obsidian Sync?
- What else could I try? Am I missing something?
- Could it be the WebSocket is not correctly stablished? How can I check?
Thank you.