10 minutes ago, SudoPacman said:

I've been getting lots of issues in the last few days with errors indicating "File fingerprint missing".

About what container are we talking about?

39 minutes ago, ich777 said:

About what container are we talking about?

 

Sorry, the MEGAsync one.

4 minutes ago, SudoPacman said:

Sorry, the MEGAsync one.

Strange, I updated the container a few days ago to be on the newest version and someone reported a similar issue but somewhat different:

 

But it seems to be fixed itself like the user reported a few posts above.

 

Maybe they introduced a few more bugs than they solved with the new version (you can read the changelog here).

Maybe it is worth creating a ticket at Mega itself and report the exact issue with a screenshot, the container uses the latest version: megasync_5.2.0-2.1_amd64.deb

7 minutes ago, ich777 said:

Strange, I updated the container a few days ago to be on the newest version and someone reported a similar issue but somewhat different:

 

But it seems to be fixed itself like the user reported a few posts above.

 

Maybe they introduced a few more bugs than they solved with the new version (you can read the changelog here).

Maybe it is worth creating a ticket at Mega itself and report the exact issue with a screenshot, the container uses the latest version: megasync_5.2.0-2.1_amd64.deb

Cool, thanks. I'll take a look at that changelog and perhaps raise an issue there if cannot find it already being reported.

Edited April 15, 20242 yr by SudoPacman

15 minutes ago, SudoPacman said:

Cool, thanks. I'll take a look at that changelog and perhaps raise an issue there if cannot find it already being reported.

Please keep me in the loop and let me know about your findings, I update the Mega container only from time to time to usually avoid such issues.

3 hours ago, ich777 said:

Please keep me in the loop and let me know about your findings, I update the Mega container only from time to time to usually avoid such issues.

Heard back from support.

I suspect it might be due to differing versions of MEGA between the originator and the importer. I guess I'll see how it goes over the next few days... if it persists I'll try grabbing the debug logs.

Response here:
 

Quote

Please make sure that you have installed the latest version of our Desktop app on all your computers .

Please log out your account (go to your Desktop app interface - Settings - Account - Log out) and then reinstall the Desktop app from this link: https://mega.io/desktop (please DO NOT un-install anything, simply install again).



[PS: Ensure you have your Recovery Key backed up in case you forget your password and need to reset it - https://mega.nz/keybackup]



If the issue persists:



- Exit the Desktop app and restart it.



- If you notice that files aren't being synced, please open the "Sync" tab of the "Settings" dialog in your Desktop app and verify that the checkbox next to your synchronization is checked. Otherwise, please check it and apply the changes.



- Check if you are syncing a drive with an unsupported or nor adequate filesystem type (VBoxSharedFolderFS, FAT/FAT32/exFAT or network drives). VBoxSharedFolderFS is not supported, FAT/FAT32/exFAT are not recommended and we are working on some issues detected with network drives, so you could still notice some inconveniences with them in the current version of your Desktop app.



- Go to the "Network" tab, click on the "Change Settings..." button on the right side of the rate limit and ensure the checkbox "Use HTTPS for transfers that don't start" is ticked.



- Also, if the transfer is very slow or it freezes, please enable desktop notifications: go to Settings - Notifications - enable "System notifications" to see if the Desktop app shows any informative message.



- If you are experiencing problems during uploads or downloads, please also check your rate limit in the "Network" tab to confirm if you have set any.



- If you are experiencing inconsistencies between the synced folders:

from the Desktop app, go to Settings - Sync - Force a full scan.

visit MEGA website (https://mega.nz), go to Menu - click "Reload your account" while holding the keyboard key Ctrl .



IF YOUR ISSUE PERSISTS:

1. Please start Terminal window, execute the following commands and send us the output - this will help us to identify your Linux distribution version.



The first command: cat /etc/os-release

The second command: uname -a

Third command: cat /etc/issue



2. Close the Desktop app (Exit).

If for some reason you are unable to exit the Desktop app using its interface, please execute the following command in the terminal: killall megasync

Please, ensure there is no the Desktop app process running afterwards (the output of the following command shall be empty: pgrep megasync



3. In order to help us with the investigation, could you please start your Desktop app from Terminal window as:



megasync --debug > ~/megasync.log



(this will send all debug messages to "megasync.log" file located in your HOME folder).

You can find a tutorial at this link:

https://mega.nz/file/fzJwWLyI#Agb3KmWjrJb0FoDjZIxfBFd87p-mA9zmFtGpYUjsl38



4. Then try to run the Desktop app and see if you are able to reproduce the issue. As soon as you see that the issue appears, please wait at least 10 minutes and only then close the Desktop app.



5. Create and send us the following documents:

- Video of the issue you are exactly experiencing, step by step.

- Screenshot of: M on your task bar - Settings - Sync tab

- Screenshot of: M on your task bar - Settings - Folders tab

- Screenshot of: M on your task bar - Settings - Network tab

- Screenshot of: Right-click on your local synced folder - Properties



6. Please attach the screenshots and your "megasync.log" (found in your HOME folder) to this email.

Please also mention if you are syncing a local, external or network drive and what is its filesystem type.



If the file is large (over 2MB) please archive that log file or alternatively upload that to MEGA through a web browser and send us back the Link with key (including decryption key).



Debug logs will greatly help us to identify and fix the problem.



We’re looking forward to hearing back from you.
 

 

On 4/13/2024 at 2:52 PM, ich777 said:

Not really...

Maybe this was just a fluke, I really can't tell why that's happening on your system. If it happens again, please feel free to reach out again.

I figured out that if I create a new folder I instantly get that message. It's not as critical now that I know I can reenable after a while (usually 1-3 hours).

9 minutes ago, iatemenchi said:

I figured out that if I create a new folder I instantly get that message. It's not as critical now that I know I can reenable after a while (usually 1-3 hours).

Please read this post, this is actually a reply from the Mega support team about the new release:

 

 

If you got further issues please try to contact the Mega support team, just for information purposes the container uses the latest version: megasync_5.2.0-2.1_amd64.deb

Hi @ich777 aside from bookmarking, how can I set in nginx the ms edge browser to redirect from https://edge.mydomain.com/ to https://edge.mydomain.com/vnc.html?autoconnect=true. Is it possible?

2 minutes ago, HHUBS said:

how can I set in nginx the ms edge browser to redirect from https://edge.mydomain.com/ to

You mean with a reverse proxy?

A example is over here:

https://github.com/ich777/docker-debian-bookworm?tab=readme-ov-file#reverse-proxy-with-nginx-example

But please put it behind a httpauth or Authelia or something like that.

1 hour ago, ich777 said:

You mean with a reverse proxy?

A example is over here:

https://github.com/ich777/docker-debian-bookworm?tab=readme-ov-file#reverse-proxy-with-nginx-example

But please put it behind a httpauth or Authelia or something like that.

 

Yes I use authentik or NPM access list. Thank you.

On 4/5/2024 at 1:30 AM, ich777 said:

Please post your docker run command.

 

docker run
  -d
  --name='jDownloader2'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="nas-mhmx"
  -e HOST_CONTAINERNAME="jDownloader2"
  -e 'UMASK'='000'
  -e 'UID'='99'
  -e 'GID'='100'
  -e 'CUSTOM_RES_W'='1600'
  -e 'CUSTOM_RES_H'='900'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:7808]/vnc.html?autoconnect=true'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/jdownloader.png'
  -p '7808:8080/tcp'
  -v '/mnt/user/appdata/jdownloader2/':'/jDownloader2':'rw'
  -v '/mnt/user/downloads/jdown':'/mnt/jDownloader':'rw'
  -v '/mnt/user/downloads/jdown':'/output':'rw,shared'
  --restart=unless-stopped 'ich777/jdownloader2' 

Sorry for the late reply, but I had no access to my server for a while -.-
I don't think this will help you, because I did change the values after I noticed...

13 minutes ago, wambo said:

  -p '7808:8080/tcp'

You have set the custom port 7808...

 

Did you change anything in the container too?

 

Can you please also include what docker run outputs when you start the container (click on the hyperlink docker run)?

On 4/17/2024 at 6:53 PM, ich777 said:

You have set the custom port 7808...

 

Did you change anything in the container too?

 

Can you please also include what docker run outputs when you start the container (click on the hyperlink docker run)?

I just checked my bookmarks what port I was using to access the VPN before and changed the port options to that, I believe the configs in the jdownloader should've kept the old values (which I probably adjusted months ago after initial setup)

About the run command: it finishes successfully.

The command finished successfully!

I think I should've stated better in my edit that I managed to fix my problem - although I don't know why port allocations changed.
 That is what I wanted to leave here (along with how to fix my problem), because maybe there was some rare issue behind it 🤷‍♂️

 

On 4/12/2024 at 12:11 AM, ich777 said:

 

 

Of course all of that will only work if you connected them with:

--net=container:OpenVPN-Client

 

...just as an FYI, I haven't actually implemented the connected containers thing yet.

 

However, since the PREVIOUS update you suggested, I haven't had to forcibly update the OpenVPN container (or manually get the Arrs to recheck their indexers and downloaders). 

 

So thanks for the help, and if I do have problems again I'll hit up the connected containers bit. 

Hi, I have a problem starting debian-bookworm docker container, it error loops with following message:

 

---Starting Desktop---
xfce4-session: Cannot open display: .
Type 'xfce4-session --help' for usage.
---Ensuring UID: 99 matches user---

 

this is a complete new install. I tried to set variable NoDisplay=true, but doesnt work

What was the changes on the Updates from Krusader and luckyBackup?

And working the luckyBackup Jobs by yours?

By me, no more. 😥

Edited April 19, 20242 yr by Revan335

1 hour ago, dstr said:

this is a complete new install. I tried to set variable NoDisplay=true, but doesnt work

Please post your docker run command.

 

1 hour ago, dstr said:

I tried to set variable NoDisplay=true, but doesnt work

Where did you set that option? Did you change anything else?

I use the container on a daily basis and it is working flawlessly.

11 minutes ago, Revan335 said:

What was the changes on the Updates from Krusader and luckyBackup?

A new noVNC base image with a minor change to make it possible to change the title from the browser window:

 

 

13 minutes ago, Revan335 said:

And working the luckyBackup Jobs by yours?

By me, no. 😥

The backup jobs are working fine as long as you are using console mode. I use it quite differently since I start the job through a user script on my backup server.

6 minutes ago, ich777 said:

The backup jobs are working fine as long as you are using console mode. I use it quite differently since I start the job through a user script on my backup server.

So, I know I'd too. But the Console Mode are not changed but he's not running.

 

I disable/enable the console mode, and tryed again this night.

9 minutes ago, ich777 said:

A new noVNC base image with a minor change to make it possible to change the title from the browser window:

We need a new Template for this Functionality?

21 minutes ago, Revan335 said:

We need a new Template for this Functionality?

No, you only need to add the variable to the template, it's not in there by default because this is in my opinion a bit of a niche use case.

Hi 

 

I have been trying to install as per instructions using Linuxservers Maria DB but Zabbix_server crashes with the following logs, Does anyone have a fix? 

 

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartConnectors": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartPreprocessors": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartTimers": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartEscalators": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartAlerters": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartTimers": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartEscalators": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartLLDProcessors": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "JavaGateway": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "JavaGatewayPort": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartJavaPollers": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartVMwareCollectors": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwarePerfFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareTimeout": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "SNMPTrapperFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartSNMPTrapper": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "HousekeepingFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "MaxHousekeeperDelete": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProblemHousekeepingFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "CacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "CacheUpdateFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartDBSyncers": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryIndexCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrendCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrendFunctionCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ValueCacheSize": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "Timeout": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrapperTimeout": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnreachablePeriod": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnavailableDelay": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnreachableDelay": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "AlertScriptsPath": '/usr/lib/zabbix/alertscripts'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ExternalScripts": '/usr/lib/zabbix/externalscripts'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "FpingLocation": '/usr/sbin/fping'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "Fping6Location": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSHKeyLocation": '/var/lib/zabbix/ssh_keys'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "LogSlowQueries": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartProxyPollers": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProxyConfigFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProxyDataFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLCertLocation": '/var/lib/zabbix/ssl/certs/'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLKeyLocation": '/var/lib/zabbix/ssl/keys/'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLCALocation": '/var/lib/zabbix/ssl/ssl_ca/'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "LoadModulePath": '/var/lib/zabbix/modules/'...added
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCAFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCRLFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCertFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherAll": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherAll13": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherCert": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherCert13": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherPSK": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherPSK13": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSKeyFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSPSKIdentity": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSPSKFile": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "ServiceManagerSyncFrequency": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "HANodeName": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "NodeAddress": ''...removed
** Updating '/etc/zabbix/zabbix_server.conf' parameter "User": 'zabbix'...added
Starting Zabbix Server. Zabbix 6.4.13 (revision 6e531c4).
Press Ctrl+C to exit.

     7:20240421:134725.249 Starting Zabbix Server. Zabbix 6.4.13 (revision 6e531c4).
     7:20240421:134725.249 ****** Enabled features ******
     7:20240421:134725.249 SNMP monitoring:           YES
     7:20240421:134725.249 IPMI monitoring:           YES
     7:20240421:134725.249 Web monitoring:            YES
     7:20240421:134725.249 VMware monitoring:         YES
     7:20240421:134725.249 SMTP authentication:       YES
     7:20240421:134725.249 ODBC:                      YES
     7:20240421:134725.249 SSH support:               YES
     7:20240421:134725.249 IPv6 support:              YES
     7:20240421:134725.249 TLS support:               YES
     7:20240421:134725.249 ******************************
     7:20240421:134725.249 using configuration file: /etc/zabbix/zabbix_server.conf
     7:20240421:134725.249 In zbx_load_modules()
     7:20240421:134725.249 End of zbx_load_modules():SUCCEED
     7:20240421:134725.249 In zbx_ipc_service_start() service:rtc
     7:20240421:134725.249 End of zbx_ipc_service_start():SUCCEED
     7:20240421:134725.249 In zbx_db_get_database_type()
     7:20240421:134725.249 In zbx_db_connect() flag:0
     7:20240421:134725.250 End of zbx_db_connect():0
     7:20240421:134725.250 query [txnlev:0] [select userid from users limit 1]
     7:20240421:134725.251 no records in "users" table
     7:20240421:134725.251 End of zbx_db_get_database_type():ZBX_DB_PROXY
     7:20240421:134725.251 cannot use database "zabbix": its "users" table is empty (is this the Zabbix proxy database?)
 

19 minutes ago, Rkpaxam said:

7:20240421:134725.251 End of zbx_db_get_database_type():ZBX_DB_PROXY
     7:20240421:134725.251 cannot use database "zabbix": its "users" table is empty (is this the Zabbix proxy database?)

Please read these lines…

 

Something seems wrong with the database.

Yes but i have tried maria DB and my sql, deleted the databases and retried multiple times but i get the same error over and over again.

does the ssd need to be btfs, zfs or xfs or doesnt it matter?