standardnotes / self-hosted

[Legacy] Self-host your own Standard Notes server for end-to-end encrypted notes and files
https://github.com/standardnotes/server
GNU Affero General Public License v3.0
341 stars 38 forks source link

I can't upload files #91

Open btk-42 opened 1 year ago

btk-42 commented 1 year ago

I can't uploads files. I have vps with nginx proxy manager and few apps. I installed standarnotes using this guide https://docs.standardnotes.com/self-hosting/docker/ I added premium subscription. I added permissions to the folders. If open fnot.mydomain.com in the browser I get Hmm. We’re having trouble finding that site. but if I open it using ip address I get white page with Cannot GET /

image image image image image

auth.logs.txt docker-compose.yml.txt files.logs.txt env.txt

Service Versions (please complete the following information): Paste the output of ./server.sh version. For example:


Container                             Repository                        Tag                 Image Id            Size
api-gateway-standalone                standardnotes/api-gateway         latest              0b4923b70da3        204MB
auth-standalone                       standardnotes/auth                latest              37bd53bb8b3c        218MB
auth-worker-standalone                standardnotes/auth                latest              37bd53bb8b3c        218MB
cache-standalone                      redis                             6.0-alpine          b5a61c880115        24.6MB
db-standalone                         mysql                             5.6                 dd3b2a5dcb48        303MB
files-standalone                      standardnotes/files               latest              90b667a6502d        206MB
syncing-server-js-standalone          standardnotes/syncing-server-js   latest              c830b1212677        216MB
syncing-server-js-worker-standalone   standardnotes/syncing-server-js   latest              c830b1212677        216MB
workspace-standalone                  standardnotes/workspace           latest              e9ae971a30cd        216MB
workspace-worker-standalone           standardnotes/workspace           latest              e9ae971a30cd        216MB
jackyzy823 commented 1 year ago

Have you check your browser's console output ? (via F12 devtools). that may give some hint.

Just a guess (CORS issue, http request is not allowed in https site) : change FILES_SERVER_URL=http://fnote.mydomain.com in .env to a https url FILES_SERVER_URL=https://fnote.mydomain.com

btk-42 commented 1 year ago

Have you check your browser's console output ? (via F12 devtools). that may give some hint.

Just a guess (CORS issue, http request is not allowed in https site) : change FILES_SERVER_URL=http://fnote.mydomain.com in .env to a https url FILES_SERVER_URL=https://fnote.mydomain.com

Hi,

I have changed the address to https and the problem you talked about popped up. console-export-2022-12-10_20-37-37.txt

I can't get into the "files-standalone" container. I use "docker exec -it 7ff1 /bin/bash" command. I get an error "OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown"

jackyzy823 commented 1 year ago

I have changed the address to https and the problem you talked about popped up. console-export-2022-12-10_20-37-37.txt

Because of Same Origin Policy, the web request from standardnotes's frontend web page can not fetch resource from fnote.mydomain.com if fnote.mydomain.com 's response do not contains Access-Control-Allow-Origin related headers.

please check you revese proxy (or CDN) configuration to see if it drops/filters it (by default files server returns with "access-control-allow-origin: *") , or you need to add it manually.

I can't get into the "files-standalone" container. I use "docker exec -it 7ff1 /bin/bash" command. I get an error "OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown"

docker exec -it 7ff1 /bin/sh

btk-42 commented 1 year ago

I have add "*add_header Access-Control-Allow-Origin ;**" to my nginx conf. But nothing changed. I checked my VPS and it isn't listen on 3125 port. Also I checked the container and it isn't listen on 3000 or 3125 port.