Mihai

Sounds like a Laravel issue. Can you DM me the container logs? There's a button on the Log column (right) in the "Docker" view in Unraid.

@cyberspectrecan you tell me exactly what behavior you get? or any errors? Otherwise it will be hard for me to fix it. Note: you will have to connect via https and port 8443 port for this to work.

I'm kind of late to the party, but to me it seems the main issue is the lack of ssl certificate on port 443 and it seems lately invoiceninja enforces https. I got it working by generating a self signed certificate. I didn't have time to create another Unraid app, but until then if anyone wants to try it out: Hit Edit on the container and change Repository field to this: maihai/invoiceninja and then hit Apply. EDIT: The way this works is that it generates a SSL certificate on the first container run which is self signed. Of course don't forget to import this certificate in y

I didn't know about it, not sure how availabie it is in Unraid. I'll check it out, thanks for the info!

I know there are other threads out there for this, but I really think docker-compose yml support would be really nice. The Docker UI thing is nice and all, but I think creating an XML file for everything I want to add can add overhead. Example: I want to use this inside Unraid, but it would be nice if it would also have UI support. https://github.com/hardware/mailserver The way I'm thinking about it an addon to the current Docker app, where it can import/edit docker-compose files.

I would use these sshd configurations + setting the users disabled. I don't think having users with empty passwords is a good idea. Thanks for the fast reply!

Btw, here's a PoC in bash (anonymized the IPs a bit, hope you don't mind ) ``` [root@taicasimaica ~]# curl -ks4 showip.net 124.122.71.51 [root@taicasimaica ~]# ssh -D 3129 -f -C -q -N bin@x.ninja -p 7127 The authenticity of host '[x.ninja]:7127 ([91.82.91.172]:7127)' can't be established. ECDSA key fingerprint is SHA256:/Kg3rfHXB/0XIa2nW5UHOLAiipUztnhNDvxAyz91CP8. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes [root@taicasimaica ~]# export http_proxy=socks5://127.0.0.1:3129 [root@taicasimaica ~]# curl -ks4 showip.net 91.82.91.172 [root@tai

If you had an SSH port opened to the internet my post I made a few minutes ago will explain this. You can try it yourself: Note: The tunnel opened will be socks5, so you'll have to configure your browser as such to actually test it.

Hello guys, I couldn't find any proper channels for announcing vulnerabilities, so i think this might be the best way to catch your attention. Apologies if there are proper channels, I did not have enough time to search for them. Upon looking at some logs I noticed: ```sshd[28121]: Accepted none for lp from 194.61.26.34 port 26028 ssh2``` Then after i took a close look at /etc/shadow I noticed almost all users don't have passwords. While they can't actually execute commands on the system, they can see information about the system: ``` $ s

Hey guys, So quick question: How do i make sure emhttpd starts at boot? Around version 6.8.7 I believe I changed the SSL port and for some reason I was starting emhttpd through /boot/config/go, but since in 6.8.1 that doesn't work anymore, I don't know why I changed it in the first place. So I was wondering if there's some setting I can revert. The only thing I remember is that at one I changed the 443 port to a non standard one 1443, and since then I've been starting it with the `go` file. AAfter upgrading to 6.8.1 at every reboot I need to login via ssh and execute emhttpd.