7 hours ago, d4man said:

I can't seem to browse to my unassigned SSD to set as my source drive -- in DSP

What are the permissions from those folders? As said before I think this is still a permission issue.

Make sure that these permissions are set to 99:100 (user:group).

I was planning on when v7 has been released +grace period (+/- 3 weeks).

 

I'm currently on v6. Guessing it's a bit to much to ask for it on v6 then? Will wait otherwise

40 minutes ago, Morthan said:

I was planning on when v7 has been released +grace period (+/- 3 weeks).

This is a pretty bad mindset that I can't understand because you are missing important security updates.

 

You have to wait or use a Tailscale Sidecar Container.

The mindset is public releases tend to have bugs in it. As a sysadmin I never jump on updates for major systems. I test them before going. As I dont have a test unraid setup, I wait 2 to 3 weeks before upgrading to see how many kinks in the cables other users get.

I know v7 has a beta track, incl RC. I also agree people already test in there, but it's a select one.

 

I don't think it's a bad mindset at all.

I guess you could say it's the same with how I handle the docker updates within unraid. I never jump on new "latest" versions, I got unraid setup to update weekly on a specific day. Sometimes it's 1 day in between updates, sometimes it's more.

 

Lets agree to disagree. I will probably update to v7 this weekend.

Edited January 21, 20251 yr by Morthan

2 minutes ago, Morthan said:

The mindset is public releases tend to have bugs in it.

LOL, did you ever think about if everyone had that mindset no one would ever find bugs, but luckily there are other people who will find bugs...

 

3 minutes ago, Morthan said:

As a sysadmin I never jump on updates for major systems. I test them before going.

I always jump to the latest beta since then I can report bugs since it is always easy to downgrade to the last version.

 

4 minutes ago, Morthan said:

I don't think it's a bad mindset at all.

I agree to disagree...

 

However this is not topic of this thread.

As said above you'll have to wait or use the Docker Sidecar method.

4 hours ago, ich777 said:

LOL, did you ever think about if everyone had that mindset no one would ever find bugs, but luckily there are other people who will find bugs...

 

I always jump to the latest beta since then I can report bugs since it is always easy to downgrade to the last version.

 

I agree to disagree...

 

However this is not topic of this thread.

As said above you'll have to wait or use the Docker Sidecar method.

Well Jeez Louise.... With all that preparation to do the upgrade, it only took about 3 minutes since clicking upgrade + reboot. And now RustDesk running with tailscale enabled. Wonderful option to have that slider and it just working! And I see we have you to thank for the Tailscale Docker integration.

Is there anywhere I can buy you a coffee / beer?

9 hours ago, ich777 said:

What are the permissions from those folders? As said before I think this is still a permission issue.

Make sure that these permissions are set to 99:100 (user:group).

Hello!

 

99 for UID -- 100 on GID for DSP and the exact same for LuckyBackup

 

 

1 hour ago, Morthan said:

Well Jeez Louise.... With all that preparation to do the upgrade, it only took about 3 minutes since clicking upgrade + reboot. And now RustDesk running with tailscale enabled. Wonderful option to have that slider and it just working! And I see we have you to thank for the Tailscale Docker integration.

Sorry for being probably rude but I don't understand that mind set most of the times.

It is pretty easy to downgrade on Unraid...

 

However I'm glad to hear that now everything is working for you.

 

1 hour ago, Morthan said:

Is there anywhere I can buy you a coffee / beer?

Sure thing, first post in this thread.

1 hour ago, d4man said:

99 for UID -- 100 on GID for DSP and the exact same for LuckyBackup

This is really strange because if the permissions are set to that it should work, have you yet tried to mount the directories with Slave? You can do that by clicking Edit on the paths in the Docker template and set it from Read/Write to Read/Write Slave.

1 hour ago, ich777 said:

This is really strange because if the permissions are set to that it should work, have you yet tried to mount the directories with Slave? You can do that by clicking Edit on the paths in the Docker template and set it from Read/Write to Read/Write Slave.

Hello again! Good news, it was a permission thing! The 'source' directory '/' was set to read only. So anything under /mnt/sourcefiles was read only, that includes basically all directories that are both source and destination folders in the array. Setting it to read/write slave caused it to fail on re-initialization, but setting it to read/write allowed a sync to happen. I remoted in to give it a try real quick, everything appears ok now, thanks for all your help, what a PITA!!!!

Edited January 21, 20251 yr by d4man

On 1/16/2025 at 11:42 PM, HHUBS said:

 

If I want to backup my files to MEGA but I also want to sync it to my local folder, like when I update a files on MEGA website it will update also my files in local folder, I should use sync and not backup right? 

 

Base on the properties, this is the permissions of the local folder I want to sync.

 

Just bumping this message. I can't still add a folder to sync. Anyone has an idea, please? Thank you.

8 hours ago, HHUBS said:

Just bumping this message. I can't still add a folder to sync. Anyone has an idea, please? Thank you.

Sorry, I've tried it now myself and even pushed an update to the container but I think it is now fully broken.

 

There are multiple issues on GitHub over here about .megaignore not being properly created, Sync/Backup not working and many other things.

I think I'll deprecate the container since it gives me much trouble over the years since it seems that with each update they push the Desktop app breaks even more.

 

Sorry to not having better news for you.

 

However what you can do is install the rclone plugin and try to sync your data that way, you even can mount a folder from Mega to Unraid.

17 hours ago, ich777 said:

Sorry for being probably rude but I don't understand that mind set most of the times.

It is pretty easy to downgrade on Unraid...

 

However I'm glad to hear that now everything is working for you.

 

Sure thing, first post in this thread.

All good. Send you a coffee

3 hours ago, ich777 said:

Sorry, I've tried it now myself and even pushed an update to the container but I think it is now fully broken.

 

There are multiple issues on GitHub over here about .megaignore not being properly created, Sync/Backup not working and many other things.

I think I'll deprecate the container since it gives me much trouble over the years since it seems that with each update they push the Desktop app breaks even more.

 

Sorry to not having better news for you.

 

However what you can do is install the rclone plugin and try to sync your data that way, you even can mount a folder from Mega to Unraid.

No worries. Thank you for giving an alternative. Thank you for your work. Appreciate it. 👍

Hey, I wanted to setup a RustDesk server for personal use and connect to other clients outside my network. 

Since my Internet is cgnat, I use a VPS (usually with NPM) to route the traffic. 
What is the appropriate way to get Rustdesk to communicate with my server / the docker?

15 hours ago, asynic said:

Since my Internet is cgnat, I use a VPS (usually with NPM) to route the traffic. 

The easiest way would be to set up RustDesk on the VPS.

 

Otherwise you could use Tailscale if you want to use the container on your Server but that of course would mean that you would need to have Tailscale installed on every machine you want to connect.

Hello, After I converted my only array disk into a unique cache disk (which contains system files like appdata), every time I connect to VNC after starting the Edge Docker, the connection gets disconnected and reloads. I’ve attached the logs, and I believe the line “/opt/scripts/start-server.sh: line 107: 84 Floating point exception” indicates that a floating point error is causing the VNC to restart. 

The image is the latest version, and I tried deleting the container and adding it back with the original template, but the problem persists. Please help me, thank you.

WebSocket server settings:
  - Listen on :8080
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - Backgrounding (daemon)
/opt/scripts/start-server.sh: line 107:    76 Floating point exception${DATA_DIR}/bin/microsoft-edge --user-data-dir=${DATA_DIR}/profile --disable-accelerated-video --disable-gpu --dbus-stub --no-sandbox --test-type ${EXTRA_PARAMETERS} 2> /dev/null
WebSocket server settings:
  - Listen on :8080
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - Backgrounding (daemon)
---Starting TurboVNC server---
---Starting Fluxbox---
---Starting noVNC server---
---Starting Microsoft Edge---
---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 0000---
---Checking for optional scripts---
---No optional script found, continuing---
---Checking configuration for noVNC---
Setting noVNC resizing to: remote
Nothing to do, noVNC qaulity set to default
Nothing to do, noVNC compression set to default
---Taking ownership of data...---
---Starting...---
---Microsoft Edge v132.0.2957.127 up-to-date---
---Resolution check---
---Checking for old logfiles---
---Checking for old display lock files---
---Starting TurboVNC server---
---Starting Fluxbox---
---Starting noVNC server---
---Starting Microsoft Edge---

52 minutes ago, VvLin-61 said:

The image is the latest version, and I tried deleting the container and adding it back with the original template, but the problem persists.

Did you also remove the folder in your appdata directory for the container?

 

I can't reproduce that over here with a fresh installed container.

 

Please try to:

1. Remove the container
2. Remove the folder for the container from your appdata directory
3. Pull a fresh copy from the CA App

 

Here is a screenshot from the container running:

 

Here is a screenshot from my log:

On 1/18/2025 at 8:34 PM, AceBurn90 said:

I have now put everything in the SABnzbd and the subdirectories as you recommended, because I like the idea of having fewer shares.
I now have a “Download” share and in it are e.g. the download folders of “jDownlaoder 2” and “SABnzbd” with subfolders for “# Incomplete ‘ and ’NZB Grabber” in the folder “# Incomplete”.
Now everything works. Thanks for the neat idea.

I must have rejoiced too soon. I'm still getting errors.

alent-diagnostics-20250125-2230.zip

8 hours ago, ich777 said:

您是否还删除了容器的 appdata 目录中的文件夹？

 

我无法在这里用新安装的容器重现它。

 

请尝试：

1. 移除容器
2. 从 appdata 目录中删除容器的文件夹
3. 从 CA 应用程序中提取新副本

 

以下是正在运行的容器的屏幕截图：

 

这是我日志中的屏幕截图：

我没有删除 appdata 中的内容;我保留它们以节省配置时间。我怀疑其中的内容可能存在问题。我会再试一次。

11 hours ago, AceBurn90 said:

I must have rejoiced too soon. I'm still getting errors.

It seems there is something messed up really badly on your system, is it possible that the mover moved all the data and something is messing with the file permissions on your system?

 

At least I think it's a permission issue because SABnzbd seems to not being able to create the directories but I wonder why that they aren't there any more.

What filesystem are you using on that drive where the downloads for everything are located?

10 hours ago, VvLin-61 said:

我没有删除 appdata 中的内容;我保留它们以节省配置时间。我怀疑其中的内容可能存在问题。我会再试一次。

You don't have to delete everything in appdata, if you want to keep your settings then just delete the bin folder in the directory for microsoft-edge

 

However I'm not 100% sure if that will resolve your issue but you can try, maybe something is messed up with the profile too.

 

Just to make sure, if you are using BTRFS or ZFS as the underlying filesystem, make sure to do a scrub from the disk/pool and also from your Docker image if you are using a BTRFS Docker image.

3 hours ago, ich777 said:

You don't have to delete everything in appdata, if you want to keep your settings then just delete the bin folder in the directory for microsoft-edge

 

However I'm not 100% sure if that will resolve your issue but you can try, maybe something is messed up with the profile too.

 

Just to make sure, if you are using BTRFS or ZFS as the underlying filesystem, make sure to do a scrub from the disk/pool and also from your Docker image if you are using a BTRFS Docker image.

What does "profile" mean? I'm using XFS, and it had been working fine until I converted this disk from an array to a cache. However, my other Docker containers are functioning normally, and I have multiple Edge Docker instances, all of which are experiencing this issue. It feels like the VNC webpage is in a quantum state—it's fine until I open it, and then it crashes and reloads with an error.

20 minutes ago, VvLin-61 said:

What does "profile" mean

It‘s a folder inside the folder for microsoft-edge which lifes in your appdata directory.

 

22 minutes ago, VvLin-61 said:

I'm using XFS, and it had been working fine until I converted this disk from an array to a cache.

Maybe something went wrong while converting.

 

23 minutes ago, VvLin-61 said:

It feels like the VNC webpage is in a quantum state—it's fine until I open it, and then it crashes and reloads with an error.

Sorry I really can‘t tell whats going on, have you yet tried to set up a completely fresh container with deleting the microsoft-edge directory?

On 1/26/2025 at 10:02 AM, ich777 said:

It seems there is something messed up really badly on your system, is it possible that the mover moved all the data and something is messing with the file permissions on your system?

 

At least I think it's a permission issue because SABnzbd seems to not being able to create the directories but I wonder why that they aren't there any more.

What filesystem are you using on that drive where the downloads for everything are located?

The strange thing is that when I stop the container and then start it again, SABnzbs works normally again. Until the next time I want to load something (days later), it doesn't work again???

 

The file system is ZFS.
I have upgraded my server with new MB, RAM, CPU and case. Then I changed the cache from XFS to ZFS. I used 2 NVme's for this. I moved the “system” and “docker” folders from the first (XFS) to the second NVme (ZFS) using a mover job. Then I formatted the first SSD in ZFS and moved the two folders from SSD2 to SSD1 using a mover job.
I don't know if this caused the problem or if many other things have caused this problem, because I have changed so much this week.