[Bug]: This file is not a cloud file not resolving.

[zehndi77]

Verified issue does not already exist?

• I have searched and found no existing issue

What happened?

On my main and test instance I do encounter various issues.

In my main instance, my productive file most of the payees and accounts were lost.
However on one client (work laptop) the file was preserved in a usable state, I could download it, reimport it at my main instance and have all transactions, accounts, payees, categories etc. still there.
It was a local file then, so I tried syncing it and registering it, nothing worked.
Also tried to reset / rebuild the stack (docker compose under portainer), still did not work.

I then tried to run a new docker host, add the stack from a fresh start, still the same issue.

Currently trying to get back a running instance from backups and try to go from there.

What error did you receive?

This file is not a cloud file
You need to register it to take advantage of syncing which allows you to use it across devices and never worry about losing your data. [Learn more]

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Microsoft Edge

Operating System

Windows 11

[youngcw]

Are you using https? Stuff like this can happen if you ignore the https warning.

What does your docker compose look like?

[zehndi77]

Hi there, thanks for the fast reply!

Yes, I am using https, though via an external nginx instance, not in docker.

The first issue was with a docker container:

The compose (new instance) is almost as described on the website, just during debugging added -DEBUG = actual:config (this was done after the issues)

version: '3'
services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest
    ports:
      # This line makes Actual available at port 5006 of the device you run the server on,
      # i.e. http://localhost:5006. You can change the first number to change the port, if you want.
      - '5006:5006'
    environment:
      # Uncomment any of the lines below to set configuration options.
      # - ACTUAL_HTTPS_KEY=/data/selfhost.key
      # - ACTUAL_HTTPS_CERT=/data/selfhost.crt
      # - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20
      # - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50
      # - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20
      - DEBUG = actual:config
      # See all options and more details at https://actualbudget.github.io/docs/Installing/Configuration
      # !! If you are not using any of these options, remove the 'environment:' tag entirely.
    volumes:
      # Change './actual-data' below to the path to the folder you want Actual to store its data in on your server.
      # '/data' is the path Actual will look for its files in by default, so leave that as-is.
      - ./actual-data:/data
    restart: unless-stopped

Thanks for your investigation!

Best

[youngcw]

Sounds like your https is working. My next guess would be that you either have an exotic browser setup, or your data volume isn't working properly and cant preserver the syncing. Both of those things have caused sync issues.

[zehndi77]

https should work, i can connect flawlessly also to other services.

my browser is opera, but I have the exact same issues on MS edge (same device) and mobile (android)
not working data volume might have been an issue, as my docker host recently ran out of space.

However I have restored the VM (docker host) to a date before that happened, and still have the same issues.
Also uploading a working copy (locally at least) I have the issues both with my "then" host, my "now" host (different dates, but the very same installation) and a completely new build, (new VM, new docker, new stack)...
How would I find such issues on the data volume?
As far as I can tell, all other services (some also newly deployed) do not have these issues.

Best

[youngcw]

your screenshot and compose file show a different directory name for the mount point. Is that expected?

[zehndi77]

not expected, but not the issue

they are on completely different machines

• screenshot = then / now machine),
• compose = new host, new docker, new stack

I am not trying to access the old data anymore, just getting a new one running with my downloaded file (.zip)

[youngcw]

I don't have any more ideas, especially if other browsers also don't work. Unless you are always deleting site data or something.

[zehndi77]

so I just today spun up a new instance outsite of docker, (lxc container) and installed the latest version. Still having the same issues. The backup files gets imported/displayed as I expect it to, but it would not let me uplpad/sync it.

Is there the possibility that something is wrong with my file/export in the beginning?
happy to share it privately if this might help.

[MatissJanis]

👋 Feel free to continue continuing to chat, but this isn't really a bug report. As such: I'll close it off.

Looks more like a misconfiguration somewhere along the way. I would recommend reaching out to the community on Discord for this sort of tech-support.

[zehndi77]

it was indeed an incorrectly configured nginx-server.
Thanks for your effort!