Internxt Drive WebDAV app?

Apps and Virtualization
1

Just curious if anyone managed to get this https://hub.docker.com/r/internxt/webdav working…
I tried to set this up as custom app, but being a Noob with this, so far no success…

Custom app with yaml: works, but remains in "Deploying" status
2

I dont have an Internxt account but that’s all that’s keeping it from failing to deploy… I used the custom yaml function and the compose file from dockerhub and it deploys “fine”. It tries to login with non existing user credentials and therefore fails.

You can basically use the compose file from docker hub, but i would add the little code part for the portal button in the truenas gui.

services:
  internxt-webdav:
    image: internxt/webdav:latest
    container_name: internxt-webdav
    restart: unless-stopped
    environment:
      INXT_USER: ""           # Your Internxt account email
      INXT_PASSWORD: ""       # Your Internxt account password
      INXT_TWOFACTORCODE: ""  # (Optional) Current 2FA one-time code
      INXT_OTPTOKEN: ""       # (Optional) OTP secret for auto-generating 2FA codes
      WEBDAV_PORT: ""         # (Optional) WebDAV port. Defaults to 3005 if empty
      WEBDAV_PROTOCOL: ""     # (Optional) WebDAV protocol. Accepts 'http' or 'https'. Defaults to 'https' if empty
    ports:
      - "3005:3005" # Map container port to host. Change if WEBDAV_PORT is customized
x-portals:
  - host: 0.0.0.0
    name: Web UI
    path: /
    port: 3005
    scheme: http
3

Strange, that (minus the portals thing) is what I had tried before posting, but it just kept cycling between “Deploying” and “Stopped”. So now I tried copy-pasting your above setup, entered of course user name and password, and same thing: cycles between deploying and stopped.

4

That’s the behaviour i was seeing as well and when i checked the app logs when it tried to deploy all it said was “invalid username or password”

5

Dang. I literally copy-pasted username and password from the settings file into internxt’s web login, and I could successfully log in. Just to make sure some typo didn’t sneak in.

Of course, I get a different error:

Logging into your account [user@domain.tld]
⚠ Error: Internal Server Error

6

OK, not a solution, but it looks like this is (currently) a known bug. A variety of people comment that they get errors with versions of this bigger than v1.5.5, while “latest” is v1.5.8
So, sometimes it’s not me screwing up :sweat_smile:
Guess I’ll have to wait until they fix this, if I still have problems, I can go bug hunting again, but in the meantime, patience is asked…

7

You could also for the time being use the working version as the tag and not latest and see if it works for you and if a fixed version gets pushed switch back to the latest tag

8

Tried that, but it seems docker hub repository only has versions back to 1.5.6 (current: 1.5.8) but the last supposedly working version according to some reporting the same issue is 1.5.5.
Tried 1.5.6, 1.5.7 and latest: no luck :man_shrugging:

Thanks for your help, though :+1:

1 Like
9

So the good thing: there wasn’t actually a bug in their docker container, but in their backend. That was fixed. So now the container mostly does what it should (may need to look into some way to secure it, but that’s another issue).

One thing that’s largely cosmetic though: it seems that the way the container is defined, the task never exits, but actually listens, so the app keeps showing up permanently as “Deploying”, even though in reality it’s running and working. :thinking: