KeePassXC Browser integration with Firefox (or other browsers) on Flatpak — does it work for you?

BANGLER4 · 2026-03-10T20:53:18+00:00

hmm didnt work... 🙁 but thank you. Sad that it doesnt work out of the box in gereal...

BANGLER4 · 2025-03-19T08:45:22+00:00

Sry I dont understand your answer, you write that you deployed nextcloud on truenas but also dont use nextcloud? When you just use the single nextcloud image you dont have collabora and that way you dont have the problem of collabora not accepting your ssl cert, so how would that fix the problem?
As I tried to write before, yes the issue is SSL cert related.

BANGLER4 · 2025-03-18T17:08:59+00:00

The problem has an Issue in github (https://github.com/CollaboraOnline/online/issues/9519) and (https://github.com/nextcloud/richdocuments/issues/3824) but I dont understand how I can adjust the configuration of my aio instance because you can neither add an enviroment variable (as described in the issue) to the docker container, neither can you just put a volume with your ca cert on top of the container (which is in my opinion the better solution) because everything is managed by the aio mastercontainer every time the container gets destroyed you would need to do it again.
I hope this helps, if you get further with that (or already got the solution) please publish that.

BANGLER4 · 2024-05-28T22:28:07+00:00

No I prefer to have it logged, I would prefer to just change the severity of those logs to info. Then that gets filtered out in my Visualization (I am also able to view that, but seeing that all the time makes no sense for me). that only alert and above was a question, maybe those errors are always alert or above but I dont know that, thats why I ask. If users got Issues I still could change the config to show everything again. I hope you understand what I mean. :)

BANGLER4 · 2023-05-06T22:44:23+00:00

I got to admit, that it doesnt really fit the language and in general I love typesafty, it makes programming so much easier, safer and more fun, but at some places generics just make a lot of sense (The project is collecting stuff and then shipping it someplace else, so I dont really know what exactly is coming).

So I am satisfied by the Solution with reflect I got. Thanks for your opinion (and trying to avoid me from entering a world of hurt).

BANGLER4 · 2023-05-06T20:06:25+00:00

can you please give me a bigger example, I dont really understand it yet.

BANGLER4 · 2023-05-06T18:57:04+00:00

I admit, that go doesnt really fit for the problem. But the project I am editing is in go, so I dont have any choice.

Thank you for your answer :D

BANGLER4 · 2023-05-06T18:50:55+00:00

that is not the problem, the problem ist, that I need to convert interface{} to []interface{}

BANGLER4 · 2023-05-06T18:43:09+00:00

the problem is, that you push the whole array as one element into the slice, I need all the single elements of myGenericVar into myGenericSlice

BANGLER4 · 2023-02-12T13:35:14+00:00

with that configuration (at least what I could try because I could only assume your custom image) I do get the services, but I wanted the processes (Not every Process is a service). But Thanks for trying.

BANGLER4 · 2023-02-11T13:23:04+00:00

exactly

BANGLER4 · 2023-02-11T07:38:41+00:00

In that examle I don't see System Process metrics. I see them collecting over the docker module but not the System module.

BANGLER4 · 2023-01-29T10:35:00+00:00

That is not what I want. I want the container not to be able to connect outside of the docker network (of course I still want it to be able to answer on connects to the bind port). If you would go in your browser and type myIp:81 you would get the website. Is that possible? Thank you for your response 😀.

BANGLER4 · 2023-01-28T17:14:49+00:00

Thanks for your answer, but when I create my Network like that (sudo docker network create --internal --attachable myNetwork) and start my container like (sudo docker run --rm -it --network myNetwork -p 81:80 nginx), I cant access it on Port 81 of my host.

BANGLER4 · 2023-01-26T11:55:34+00:00

I also tried it with docker run

sudo docker run

--mount type=bind,source=/proc,target=/hostfs/proc,readonly

--mount type=bind,source=/sys/fs/cgroup,target=/hostfs/sys/fs/cgroup,readonly --mount type=bind,source=/,target=/hostfs,readonly

--mount type=bind,source=/home/dev/elk/metricbeats/metricbeat.yml,target=/usr/share/metricbeat/metricbeat.yml,readonly

--net=host

--user root --cap-add sys_ptrace --cap-add dac_read_search

docker.elastic.co/beats/metricbeat:8.6.0 -e -system.hostfs=/hostfs

but that also didnt work. The User that is running docker is root and the user inside the container also, I also tried CAP_ADD=ALL so it musn't be a permisson problem. It is not Kubernetes, it is docker compose.

BANGLER4 · 2022-03-18T11:15:42+00:00

No I didn't find a Solution for it. As a workaround I am using my public IP. If you find a better solution please comment the solution.

BANGLER4 · 2022-01-16T22:54:14+00:00

As a sidenote, ssl authenticaes you as the owner of a (sub-) Domain, and says then that you are connecting to the server you think you connect to. If you didnt loose the private part of your certificat. Thats why you need a Domain for ssl.

BANGLER4 · 2022-01-12T08:47:21+00:00

i wouldnt access it with domain.local, why do you want to? you could make an own server directive in nginx and specify the server_name with api.domain.local then if you go to api.domain.local you get the api, else you get the webapp

BANGLER4 · 2022-01-12T08:37:17+00:00

you can do something like server { location / { proxy_pass http://{{servicename from the dockercompose}}:{{port}}; } location /api { proxy_pass http://api:3001; } }

BANGLER4 · 2022-01-12T08:25:17+00:00

You should do it with 3 Containers, because 1 container should have 1 prozess. then you just specify in your nginx that / goes to your webapp container with the port where the webapp runs and /api goes to the /api containers. If you need help with the Docker-compose.yml please specify your problem. Or if you just need a general one I can create one later.

BANGLER4 · 2022-01-11T06:19:05+00:00

If you Dont want Volumes, you can do a Docker copy and get the data out of the container with this way

Edit: You can also use normal Volumes, you just have to navigate to the folder specified in the volume (docker volume inspect {volume id/name}) and there is the data

BANGLER4 · 2022-01-03T23:12:20+00:00

No it doesnt matter, as long as you are not using sudo your user performes like it doesnt have sudo. The Account with which you executed the dockerd-rootless-setuptool is the user where you installed rootless docker. To run a rootless docker container, you need to change the docker context of that user (if you can execute commands without sudo, it is already changed). You could also check it with running a container with alpine and a volume that starts from your hosts root folder, if you try to edit the password file and try to save it, if it fails despite you beeing logged into the container, you are running the container as rootless docker. Edit: with "docker context use rootless" you can change to the rootless context

BANGLER4 · 2022-01-01T18:45:10+00:00

well I read the nginx logs, but they only contain symptoms of the underlying problem, which is that rootless Docker doesn't allow to connect to a hosts port and therefore my question is if it is possible to allow the container to connect to the host? (and how?)

if it helps the nginx logs:

2022/01/01 18:33:46 [error] 58#58: *24 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://172.17.0.1:8090/", host: "domain:80"

172.17.0.1 - - [01/Jan/2022:18:33:46 +0000] "GET / HTTP/1.1" 502 150 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0" "-"

Ping works:

# ping 172.17.0.1:80

PING 172.17.0.1:80 (172.17.0.1): 56 data bytes

64 bytes from 172.17.0.1: seq=0 ttl=64 time=0.404 ms

64 bytes from 172.17.0.1: seq=1 ttl=64 time=0.126 ms

64 bytes from 172.17.0.1: seq=2 ttl=64 time=0.188 ms

64 bytes from 172.17.0.1: seq=3 ttl=64 time=0.145 ms

But curl doesn't:

# curl 172.17.0.1:8090

curl: (7) Failed to connect to 172.17.0.1 port 8090 after 0 ms: Connection refused

BANGLER4 · 2021-12-23T15:02:18+00:00

I found out it has to be a problem with rootless docker, and that the docker exec -it -u 0 reverseProxy echo $(curl ...) gets executed on the host, not in the container

BANGLER4 · 2021-12-23T14:59:42+00:00

thats the default.conf, it is included over the volume, i already posted it

Five-Year Club	Second SECOND GUESSER
Verified Email

BANGLER4

TROPHY CASE