Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About IxsharpxI

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-3 - Lo ader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - Proxmox 6.0-4 - Additional comments: e1000e network adapter
  2. Could i open those seperately for the Drive specifically? and just leave the reverse proxy in tact? EDIT: I just tried another instance at my house.. no extra port forwarding just nginx and it connected although warning of self signed certificate. Its gotta be something specific to his install or network. I assume xpenology typically works find with drive without a SN? His network is double NAT but ive just been port forwarding accordingly.
  3. I’m having trouble connecting the drive app on my Mac. It works fine on phone and from browser when Remote and on local network. But using my domain name the drive app says it cannot connect. It’s going through my nginx proxy manager and only 80 and 443 forwarded. Anyone got any ideas or seen this before?
  4. I have the same issues..except mine is running through nginx proxy manager. I can even log in on the app just fine using the domain name w/ no port number, but not on a PC or mac.
  5. Alright ive determined its something with my hardware that doesnt like 6.2. I tried a 6.1 loader and it worked. It also showed me on the find.synology.com prompt that it actually reads a booting kernel message. This doesnt happen when trying 6.2. Hardware is Dell r610 x5670. What could the problem be?
  6. Got past step 4 but not I’m at the page to go to find.synology but can’t find with assistant or router dhcp page
  7. Im stuck at step 4 where i am supposed to save synoboot.img locally onto proxmox server. When i try to go into /var/lib/vs/images there is not vms there its just empty