showstopper

Members
  • Posts

    153
  • Joined

  • Last visited

Posts posted by showstopper

  1. 2 minutes ago, Taddeusz said:

    Are you using a Microsoft account? Are you using Windows Hello to login even with just a pin? If so you have to login with your password at least once so that it’s cached. After that RDP should work fine and you can go back to using Windows Hello to login locally.


    Thank you for replying - I fixed it and edited my post

  2. Hi guys,

     

    So I just installed this and I have it working to Windows Server 2019 and SSH to unRAID. However I can not get this working to my (non-domain) Windows 11 PC. Has anyone got this working to Windows 11? I can RDP from a different windows machine, but guacamole just nevers does it.

     

    EDIT - Just to say that i have Security mode set to NLA and Ignore Server Certificate checked.

     

    EDIT2 - OK I got this working. Bit of a strange one. I had enable WOL and the mac used hyphens (-) this seemed to stop guacamole making the RDP connection. I changed it to colon (:) and RDP started working.

  3. Just now, Allram said:

    I run this on Windows Server 2022 and it works awesome.

    Just changed what the OP said :)

    I use RDP via Apache-Guacamole.


    I did try this and the mstsc (remote desktop) never actually connected, so I switched back.

    I don't know why it would have done that.

  4. 1 hour ago, Killabee44 said:

    I am having the same issue. Recently lost all of my containers and had to reinstall (long story) but now mariadb isn't working and I don't have a .sock file either. I do see my databases in the app folder though.

     

    Also I was using the linux version but now would like to move to the official one. Is it as easy as copying the database files to the official mariadb appdata folder? Thanks!

     

    Edit2: Another layer to this. I have multiple databases in the linuxserver install of Mariadb as well. I know now not to ever do this but is as easy as installing the two official Mariadb containers (with different name and paths) and then copying the different DB folder from the linuxserver into the data folder of each new official Mariadb install?


    Hey.

    So unfortunately these forums seem to be a bit of a ghost town recently! I am sure I have done something wrong with my new server setup that has broken everything, and I initially blamed macvlan. I actually think the mover is breaking my dockers. So, today, I will be deleting some dockers, and making sure only the cache drive is used for Appdata, Domains & System. I'll kick off the mover, then delete some dockers, and start again.

     

    I think with the multiple databases, you can do it that way, but I think they recommend 1 mariadb per database is that it is potentially easier to manage! I'm not really a db guy so I am not sure if you can do what you want to do. It sounds like a permissions issue though.

  5. On 7/26/2023 at 1:49 AM, Antoni Żabiełowicz said:

    Hello, I was running official nextcloud with mariadb and redis for seven months without any issue. After todays nextcloud docker image update container won't start. Does any of you expirienced such problems lately? Thanks for any help.

    Zrzut ekranu 2023-07-26 o 02.46.17.png


    Yep I think there is major error with fresh installs of nextcloud at the moment. I have tried LSIO and official MariaDB and Nextcloud dockers. Both install perfectly fine, until you bounce MariaDB AFTER install nextcloud. It then seems to corrupt the MariaDB into oblivion. I've been working on this a couple of days now, and I am stuck.

  6. I am getting some very strange results trying a fresh MariaDB and NextCloud install. Everything seems to work until the nextcloud install. I check the mariadb logs and I can no longer log into the database and the log keeps getting filled with *.err files. I have tried maybe 4 times with the same result each time. I am now going to try a fresh install with the official docker versions.

  7. Hi guys - hoping someone can help me. I changed from macvlan to ipvlan and everything seemed ok. I then tried to update nextcloud and it seems to want to create a new admin account. After further diagnostics I believe the issue is related to MariaDB.

    I have these error message repeating in the logs:

     

    230723 18:04:59 mysqld_safe Logging to '/config/databases/e571c6533173.err'.
    230723 18:04:59 mysqld_safe Starting mariadbd daemon with databases from /config/databases
    Caught SIGTERM signal!

     

    I tried to login as root user and i get this error:
     

    root@e571c6533173:/# mariadb -u root
    ERROR 2002 (HY000): Can't connect to local server through socket '/var/run/mysqld/mysqld.sock' (111)
    root@e571c6533173:/# 

     

    Can anyone point me in the right direction here? I do not seem to have a 'mysqld.sock' file, so I am not sure where I need to start?!

  8. I have had this issue for a while and assumed it was the CPU. I've upgraded but it doesn't seem to have made any difference.

    My windows server VM's take A LONG time to boot and then enable services. I have logs in the event viewer regarding delays to write files. Can anyone see anything in the logs that could help me?

     

    It is strange as they seem to work fine, then they seem to crawl to almost a halt, and then speed up again. I am wondering if it is a ssd error. Everything else on the server now seems ok, after updating to 6.12.1.

    Really hoping someone can shed some light on the issue! Diagnostic files attached.

    unraid.zip

  9. Hi guys,

     

    My system has been running fine for ages but the last couple of days I've had some brown-outs (I know I am looking into a UPS). Anyway everything starts up except plex. I manually started it and it worked. Then another power-cut and I tried to restart plex and then the docker page would not display anything. It just had the unraid logo constantly.

     

    So I tried to edit the docker and now it looks like it is stuck like this image.

     

    Any ideas what is wrong?

     

     

     

    image.png

  10. Hi guys,

     

    So I changed my cache drive a couple of days ago and everything now seems to be working well, other than my plex docker. This fails to start when the server is rebooted, but will start when I manually start it. Any ideas what to try?


     

    To support LSIO projects visit:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------
    
    User uid:    99
    User gid:    100
    -------------------------------------
    
    **** Server already claimed ****
    **** permissions for /dev/dri/card0 are good ****
    Docker is used for versioning skip update check
    [custom-init] No custom files found, skipping...
    Starting Plex Media Server. . . (you can ignore the libusb_init error)
    [ls.io-init] done.
    Jobs: Exec of ./CrashUploader failed. (2)
    The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
    The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
    The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
    The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
    The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.