• Posts

  • Joined

  • Last visited

About exico

  • Birthday August 4


  • Gender
  • URL
  • Location
    North East Italy

Recent Profile Visitors

535 profile views

exico's Achievements


Newbie (1/14)



  1. Yeah. mine too. I was wondering why one of the services just died and i checked the db connection... Not sure why it worked but i changed the repo from linuxserver/mariadb to linuxserver/mariadb:alpine-version-10.5.12-r0 (an older version) and then changed it to linuxserver/mariadb:latest and works. Not ideal i know but works. Logs for the error points to a fail in innodb 210825 18:56:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored 2021-08-25 18:56:18 0 [Note] /usr/bin/mariadbd (mysqld 10.5.12-MariaDB) starting as process 4703 ... 2021-08-25 18:56:18 0 [Note] InnoDB: Uses event mutexes 2021-08-25 18:56:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-08-25 18:56:18 0 [Note] InnoDB: Number of pools: 1 2021-08-25 18:56:18 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2021-08-25 18:56:18 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2021-08-25 18:56:18 0 [Note] InnoDB: Using Linux native AIO 2021-08-25 18:56:18 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2021-08-25 18:56:18 0 [Note] InnoDB: Completed initialization of buffer pool 2021-08-25 18:56:18 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.21. 2021-08-25 18:56:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2021-08-25 18:56:18 0 [Note] InnoDB: Starting shutdown... 2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' init function returned error. 2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2021-08-25 18:56:18 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-08-25 18:56:18 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2021-08-25 18:56:18 0 [ERROR] Aborting 210825 18:56:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
  2. Fvtt docker is on port 30000. Is a web application based on nodejs for D&D and more
  3. Im having a problem where i can access fine fvtt trough a domain but when i paste the key and get to the configuration to start a world the "play" button goes grey and do nothing. If i access directly trough unraid:port everything works. Im using this proxy manager: As options i enable Cache assets, Websocket support, Force SSL (letsencrypt) and i added in the custom configuration this bit: add_header Referrer-Policy "same-origin" always; add_header Access-Control-Allow-Origin https://domain.redacted always; client_max_body_size 1024M; fastcgi_buffers 64 4K; set $upstream_app FoundryVTT; proxy_max_temp_file_size 1024m; The complete automated config file looks like this: # ------------------------------------------------------------ # domain.redacted # ------------------------------------------------------------ server { set $forward_scheme http; set $server ""; set $port 30000; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443; server_name domain.redacted; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem; # Force SSL include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-2_access.log proxy; error_log /data/logs/proxy-host-2_error.log warn; add_header Referrer-Policy "same-origin" always; add_header Access-Control-Allow-Origin https://domain.redacted always; client_max_body_size 1024M; fastcgi_buffers 64 4K; set $upstream_app FoundryVTT; proxy_max_temp_file_size 1024m; location / { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } proxy.conf: add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass $forward_scheme://$server:$port; options.json { "port": 30000, "upnp": false, "fullscreen": false, "hostname": "domain.redacted", "routePrefix": null, "sslCert": null, "sslKey": null, "awsConfig": null, "dataPath": "/foundry/data", "proxySSL": true, "proxyPort": 443, "minifyStaticFiles": true, "updateChannel": "release", "language": "it.FoundryVTT - it-IT", "world": null } On this proxy i have all sort of hosts: plex, wikijs (that runs on nodejs and has no problems of sorts), my firm site, a gitlab etc and foundryvtt is the only one I am having problems with. What Im doing wrong?
  4. Disabled "Host access to custom networks" and now i can access everything except one docker but i will figure it later
  5. I did not, just tried and nothing changed. Just an hypotesis, can the setting "Host access to custom networks" set to enable in the docker settings be a problem? I will have to wait to stop dockers to test this atm cause there is a task running
  6. Im using
  7. Yeah, my config includes allowed ips: [Interface] PrivateKey = REDACTED Address = [Peer] PublicKey = REDACTED PresharedKey = REDACTED AllowedIPs =, Endpoint = REDACTED:51820 NAT is on Yes as per screenshot What I'm trying to access is something. I tried the server ipmi, the web interface of the switch, pfsense interface on the router. Nothing pops up, just the unraid works and shows up Everything worked fine before...
  8. Well it was already on Remote access to LAN I can connect but i can access only the unraid server and nothing on the lan
  9. Here's the output: [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add dev wg0 [#] ip -4 route add dev wg0 RTNETLINK answers: File exists [#] ip link delete dev wg0 Guess that the error is File exists what does that mean?
  10. Im having a strange problem and i cannot figure out whats wrong I edited a peer recently and from that point forward i cannot activate the tunnel. I did try to save it, remove it and re-import but whenever i add in "peer allowed IPs" the LAN network with x.x.x.x/24 the tunnel wont activate. Tunnel: Local tunnel network pool: Local tunnel address: Endpoint: [redacted, static ip]:51820 Local server uses NAT: No (i tried with Yes, nothing changes) First Peer: Peer name: something Peer type of access: Remote access to LAN Peer tunnel address: Peer allowed IPs: Whenever i put ( is the lan) Peer allowed IPs:, The tunnel wont stay On, if i press on the button it moves but if i F5 the page or go to another and come back is OFF. Syslog just says that the tunnel turned on and off There is a more useful log for wireguard? There is nothing in /var/log On this machine i have already a tunnel server to server that works flawlessy
  11. Im an idiot 😆 Ping replied, got an handshake. I forgot that wireguard does not initiate the connection until there is a request. Gonna change the keys, thanks
  12. Hello! I've been trying to setup a server to server access that from what i understand is like lan to lan but without the routing. I followed the steps in the first post but i cannot get an handshake. Heres what i configured (i will change keys later when i get this working) I have static IPs in both locations that i redacted for obvious reasons. I forwarded port 51830 in both pfsenses. For context, in both locations i have already a "remote access to LAN" setup with various clients and works fine (on a different port/tunnel obviously) I cannot get a handshake, do you have any idea of what im doing wrong?
  13. For those who had this problem: UniFi Controller startup failed We do not support upgrading from 6.2.23. Checkings the logs in /logs/server.log: [2021-05-13T12:09:08,198] <localhost-startStop-1> INFO db - DB version (6.2.23) different from Runtime Version(6.1.71), migrating... [2021-05-13T12:09:08,205] <localhost-startStop-1> ERROR db - We do not support upgrading from 6.2.23. I searched around in the data folder and i found that the "DB version" is just a text file. If you change the version in the text file it just skip the check and migration. You can find the file in /data/db/version Just edit it with notepad++ or whatever editor that is not Windows notepad and change it from 6.2.23 to 6.1.71 Save and start the docker. I dont know if this can cause problems in the long term but at least you can start back up the controller
  14. You are right, it's the stupid vmware player vm that is broken. I tried with a vm in Unraid and it loads fine, i did not try with a physical machine yet because i use my desktop as work pc and my notebook has no ethernet. I wonder why vmware player doesnt work
  15. I'm struggling to boot live media from the netboot docker and i have no idea what I'm doing wrong. - I set up the live endpoint correctly (i had to reroute port 8080 to 8069 cause it was already used in another container but it works. i can navigate it fine) - I downloaded the assets (in my case i tried popos 20.04 and ubuntu mate 20.10 and i can see them in etc ) - I set up a vmware vm that boot into pxe and i get this error (see attached image). I get the error whenever i boot popos or ubuntu mate live I tried Ultimate boot cd and works ( i had to download it manually and change the name cause there is a version mismatch in netboot config files) I tried ubuntu network install 20.10 and works, gparted works, clonezilla ubuntu stable works VM has plenty of ram (8G) and disk (64G) and is in bridge mode so it has its own ip and mac DHCP is provided by my pfsense and is configured correctly