SmartPhoneLover

Members
  • Content Count

    18
  • Joined

  • Last visited

Everything posted by SmartPhoneLover

  1. Hello guys, Someone knows how to resize widgets in DSM? And if it's actually possible? In that case, I need to resize the one that displays HDDs information. To clarify what I need:
  2. I just wanted to know and see the difference that Portainer seems to offer to manage them. I'm just curious 😉 And, as @Lethal mentioned before, to be able to manage containers without logging in to DSM
  3. Hi, thank you for the answer. Yes, that was what I ended up doing.
  4. Hi all, I'm trying to set up Portainer within Docker, but I have a problem trying to add and also make that change permanent, to allow Portainer look into '/var/run/docker.sock' for the local Endpoint. I have tried both ways, I mean: - Create and configure the container using the Synology Docker app (GUI), but here, as /var/run is a root directory, I can't load the 'docker.sock' file. - Create and configure it within Terminal (PuTTY): docker run -d -p 32770:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /volume1/docker/Portainer:/data portainer/portainer. But the docker.sock link just disappears after starting it everytime. I have tried to make a symlink of /var/run dir to one of my user volumes so I can access these files easily, but docker.sock image was not shown there, so couldn't link it within Docker container settings.
  5. Hi all, Hope you can help me on this 😅. I successfully installed Bitwarden via Docker (mprasil/bitwarden), and it is currently running perfect. But within the NAS, or accessible from the same local net via web browser. The problem I'm facing right now is that I can not connect to my Bitwarden DB (NAS) from my smartphone (app), nor using the standalone Windows app. Both, Windows & Android apps, requires you to connect using a https protocol. But I don't know how could I set it up within Docker enviroment. I attached you some screenshots about the current config I have. It's in Spanish lang, but easy to understand if you know Docker. Note: I use it in a LAN without internet access, so local access only. Thank you.
  6. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1 (latest update) - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: as you show on my other posts
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DS918+_6.2.1-23824 (Update 4) - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VMWare/ESXi - Additional comments: Installed latest available update (DSM 6.2.1_23824 Update 6) + VMware Workstation 15 + PC Desktop (AMD Ryzen, W10)
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DS918+_23739 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VMWare/ESXi - Additional comments: Installed latest available update (DSM 6.2.1_23824 Update 4) + VMware Workstation 15 + PC Desktop (AMD Ryzen, W10)
  9. - RESUELTO - Clic aquí para ir al tema en cuestión. (english)
  10. Hi thank you for asnwering. I already solved it. What was actually happening, at least on 6.x version was that it didn't recognize the net card, as you mentioned. So, after changing the NIC type to 'e2000e' on the vmx file, it worked. And also, created a custom VMnetx adapter to manually bridge the guest because I wanted to assign it a static IP address within my 'real' network, so be detected from my host. Apart from this, had to move the SATA disk (vmdk image) of the Loader to the first place, in the BIOS boot order. And worked! And talking about 5.2 (last available), I just needed to manually set the CD-ROM (virtual) to be in the first place (order), because I don't know why, but VMware was just preventing it to start after installing the DSM file. So, it worked too! These are the Expenology systems I'm currently using to test them, and know about this beautiful NAS system: - 5.2: XPEnoboot_DS3615xs_5.2-5967.1 (Loader) / DSM_DS3615xs_5967 (PAT) - 6.2: Jun's Loader v1.03b DS3617xs (Loader) / DSM_DS3617xs_23739 (PAT)
  11. Indicadme si deseas alguna especificación por parte del PC donde se esta intentando instalar, en caso de que sea necesario. Pero, lo básico: - Windows 10 Pro (última build) x64 - AMD Ryzen 5 2xxx (obviamente tengo la virtualización habilitada en BIOS)
  12. Muy buenas Hace unos días me dispuse a probar XPEnology en mi equipo PC de escritorio usando VMware (y VirtualBox), y no hay manera de hacerlo funcionar. Con todas las versiones falla. Es más, con Loader's mayores a 5.2, es decir, 6.x.x Synology Assistant ya ni siquiera llega a encontrar ninguna IP una vez iniciado el server. Las que si me funcionan, pudiendo iniciar es, por ejemplo, la 'XPEnoboot_DS3615xs_5.2-5644.4' (ISO), usando su 'DSM_DS3615xs_5644' (PAT). Pero tras la instalación manual de su DSM, una vez la máquina es reiniciada, nunca llega a reiniciarse correctamente. Queda el cursor horizontal en pantalla sin POST. Ocurre tanto en VMware como VirtualBox. Por si os sirve, algunas especificaciones de cómo creo dichas máquinas: - OS: Linux (voy jugando con el Kernel 2.x/3.0/4.0 a 64bits, según versión Loader) - RAM: 1024MB - CPUs: Por lo general 1/1 (o 1 en VirtualBox), hasta ver como funciona el sistema en si, cosa que aún no he conseguido - Loaders: Para los Loaders que ya disponen del ISO arrancable (5.x) lo uso como medio de arranque; en cambio, usando Loaders 6.x.x, los convierto de IMG a ISO, seleccionando la partición nº 1 de cada versión que me descargue, y para ello uso PowerISO. También he probado StarWind V2V Image Converter, especificando éstos como unidades de almacenamiento (HDD) de inicio, convertidas a archivos VMDK. - HDD: He probado con SATA y SCSI. (el que se usará para instalar el PAT, ¿verdad?) - Red: Tanto en VMware como VirtualBox, Bridge/NAT/Host-Only funcionan, detectándome los servers en Synology Assistant. (Loaders 5.x.x) Muchas gracias.
  13. Hi all, I'm just new on this community, and also to the XPEnology world Hope you can help me on the problem I'm facing right now while trying to mount it using VMware Workstation (Pro) on a Desktop PC, and 6.2(.1) Loaders, to be able to use, of course, DSM 6.2. If possible. These are the steps I followed until I got stuck on Synology Assistant not finding any device (IP): 1. Extract Loader's ZIP file, and convert 'synoboot.img' to VMDK image (synoboot.vmdk). As I don't want to boot from a USB drive, and need VMware to boot it. 2. Create the VM: Linux 4.x-64bits, I/O Controller LSI Logic, Virtual Disk Type SATA (both synoboot.vmdk and storage to be used to install it). 3. Set Network Adapter preferences to 'Host-only', as 'XPEnoboot_DS3615xs_5.2-5967.1' was working fine. And after turning it on, Synology Assistant can't find anything. But it's correctly started, I think. Thanks