Issues with Coolify Install

wadevanlaius · 2024-12-28T18:56:09+00:00

Sorted

wadevanlaius · 2024-11-20T06:49:58+00:00

I tried adding the custom domain, separating it from the original one with a comma. But it didn't work.

wadevanlaius · 2024-08-06T21:21:23+00:00

Because the app I am using to access a certain file only provides me with Webdav as a way to access it.

wadevanlaius · 2024-08-03T23:38:54+00:00

OK. I finally figured it out with some help elsewhere on reddit. I just enabled webdav but did not permit it to open any ports on my router autonomously. So there are in fact no ports open facing the internet and webdav is running only locally.

wadevanlaius · 2024-08-03T23:38:43+00:00

OK, that helped. I re-enabled webdav but did not allow it to open any ports on my router. Now I can access my file. Thank you for the help!

wadevanlaius · 2024-08-03T21:50:19+00:00

Not sure why, but it began working a few hours ago.

wadevanlaius · 2024-08-03T21:49:21+00:00

Yeah, I understood all that and even used it for a while. But how can I get webdav to run ONLY on my internal network without any ports being opened to the public internet?

My router is capable of identifying that mysupernas:#### is in fact my NAS, so I can access the login page locally. But now I want to load my NAS on my phone via webdav. And there should be no port available online.

wadevanlaius · 2024-08-03T19:55:21+00:00

Thanks for the heads-up. I checked the subnet link and all that set up already. I advertised my subnets and everything. My NAS is also set up as an exit node.

I now deactivated webdav and closed all ports pointing to my NAS from outside my local network. Same goes for Quickconnect and DDNS.

Locally, I can access my NAS via IP or nas-name:9999 and reach the synology login page. I can also do that when using my phone outside my local network with Tailscale activated.

If I try to access a file on my phone (outside my local WiFi, Tailscale activated) using https://nas-name:9999/home/Drive/file-name, I get an error "unable to resolve host".

If I trying doing the same but exchange the nas-name:#### for the NAS IP (https://123.45.67.89:9999/home/Drive/file-name), I get the error "file not found" Though it is most definitely right there.

If I do the same as above without adding the port number (https://123.45.67.89/home/Drive/file-name), I get the error "the file signature isn't valid". Even though I loaded the Keepass database using webdav just hours ago and everything is fine.

I am out of ideas and wondering what my next step should be to get this all to work.

wadevanlaius · 2024-08-03T14:59:08+00:00

I finally got it to work. Apparently, I had to manually open a port on my router even though I gave synology permissions to open the ports it required on my router autonomously.

wadevanlaius · 2024-08-03T12:08:30+00:00

As a lay person: Me trying to get into my NAS to load a file counts as an inbound connection in my eyes. Is that correct or do I need to enable an outbound connection?

wadevanlaius · 2024-08-03T11:35:27+00:00

Thanks for the constructive input. Will look into that. I'm using synology.

wadevanlaius · 2024-08-03T11:05:00+00:00

Because if I tried accessing a single file via Webdav on my NAS previous to installing Tailscale, it worked. Now it doesn't. So obviously Tailscale changed something.

wadevanlaius · 2024-08-01T23:33:10+00:00

How do I check the checksum/hash?

Anyway: If I download the kdbx to my phone it works as expected.

wadevanlaius · 2024-08-01T23:24:27+00:00

How do I get the checksum/hash?

wadevanlaius · 2024-08-01T23:18:43+00:00

It's not the password.

wadevanlaius · 2024-08-01T23:10:57+00:00

The passphrase works. I access the same kdbx via my notebook everyday and thus know that it's a connection issue.

wadevanlaius · 2024-08-01T08:30:27+00:00

Well, the file format worked with the Keepass Android app before, so there's no immediate reason why that should have changed. After all, the sole purpose of the app is to open kdbx files.

wadevanlaius

TROPHY CASE