search

acheong08 / obi-sync

Reverse engineering of the native Obsidian sync and publish server
https://obsidian.md/sync
GNU General Public License v2.0
1.02k stars 58 forks source link

Docker compose issue #20

Closed yorurr closed 1 year ago

yorurr commented 1 year ago

Hi there,

First congrats on the progress so far, this project looks promising! I tried to run the sync server with docker-compose file provided in the Wiki but to no avail.

Environment info: Two VM's running Debian 11 x64, Docker 24.0.5, using the docker compose config as-is.

Issue encountered: The sync server was started with docker compose up, and was listing on 127.0.0.1:3000, which was exposed as port 3000 on the host. I tried access the server using both IP:3000 and nginx reverse proxy: the IP:3000 returns "curl: (56) Recv failure: Connection reset by peer" no matter accessing from localhost or Internet, and the nginx proxy shows 502 bad gateway, which means it's not talking to the upstream.

I've checked the provided docker-compose file, it's pretty straight-forward, and it looks just fine, no idea why it's not working as intended.

johe123qwe commented 1 year ago

I have the same problem

acheong08 commented 1 year ago

The sync server was started with docker compose up, and was listing on 127.0.0.1:3000

Listen on 0.0.0.0:3000 inside docker. localhost might not be exposed correctly

yfffy commented 1 year ago

The sync server was started with docker compose up, and was listing on 127.0.0.1:3000

Listen on 0.0.0.0:3000 inside docker. localhost might not be exposed correctly

This may be the cause, the docker-compose file's ENV entries specified ADDR_HTTP=0.0.0.0:3000, but inside the container it listend on 127.0.0.1

image