Jump to content
XPEnology Community

hoppler

Member
  • Posts

    50
  • Joined

  • Last visited

  • Days Won

    16

Posts posted by hoppler

  1.   

    On 2/3/2020 at 12:32 AM, Pandadoo said:

    Hi everyone,

     

    So, if, like me, you just have an error like "ssl_error_rx_record_too_long" think about http connexion.

     

    PS : my connexion to DSM is in https (in fact, every page is in https, i don't explain why that didn't work properly..

     

    Hi,

     

    this error usually means you have a misconfigured local proxy. Those local proxys are in some cases created by your antivirus/firewall software which links inbetween an SSL/TLS connection but in your case just broke it. If you only have the windows onboard antivirus solution installed an nothing else maybe its worth lookin into possible trojans/viruses which sniff your connection

  2. Hi,

     

    if you havent already tried: you could use https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ which made it possible to use the HP Gen8 MicroServer as it contains working drivers. 

     

    There wont be anymore updates for 6.1.7 so your system will have security issues which can be maybe ignored if its only a system in a local network.

  3. 8 hours ago, nqn_vnn said:

    I'm getting error code 103. Someone who knows what to do? Thanks all.

     

    100 Unknown error
    101 Invalid parameter
    102 The requested API does not exist
    103 The requested method does not exist
    104 The requested version does not support the functionality
    105 The logged in session does not have permission
    106 Session timeout107Session interrupted by duplicate login

     

    Either ActiveBackup is not installed or its deactivated

  4. 15 hours ago, anibalin said:

    Thanks hoppler for this workaround. I feel like goofy here since somehow it tries to google te url instead of going directly to it. Tried http and https. Odd enough it opens the status successfully.

     

    Hi,

     

    the issue is not because of you, but there is a hidden character between PORT and / which causes the browser to search the url instead of opening it. Here is a version without the hidden character:

     

    https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS

  5. 35 minutes ago, Sbansar said:

     

    Have u solved the problem ?

     

    I met the exactly same problem with those errors,  and I login system before activating ,  It's works!

     

    Hi,

     

    the user has to be in the "administrators" group and if the password contains special characters like +?%, you have to encode it first. https://meyerweb.com/eric/tools/dencoder/

     

    Example:

     

    Username: test

    Password: 1+?%abc

    has to be encoded to: 1%2B%3F%25abc

     

    Result:

    https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=test&passwd=1%2B%3F%25abc

  6. On 1/25/2019 at 7:53 AM, Neos said:

    Appear this error:  {"error":{"code":400},"success":false}

     

    The error codes for login:

     

    100 Unknown error.
    101 The account parameter is not specified.
    400 Invalid password.
    401 Guest or disabled account.
    402 Permission denied.
    403 One time password not specified.
    404 One time password authenticate failed.
    405 App portal incorrect.
    406 OTP code enforced.
    407 Max Tries (if auto blocking is set to true).
    408 Password Expired Can not Change.
    409 Password Expired.
    410 Password must change (when first time use or after reset password by admin).
    411 Account Locked (when account max try exc

    • Thanks 2
  7. 34 minutes ago, raceboy said:

    it will hold for any upward updates ?

     

    Its what the apps do after you logged in successfully. therefore its no "hack" but the official way to activate those programs. as long as synology does not change that way it will uphold

  8. 3 hours ago, rain_cs said:

    Does this method works for Active Backup Office365?

     

    • Login (replace URL, PORT, USER, PASS)
      • https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS

     

    for ActiveBackup its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" 

     

    for Office365 its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=get_activation&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="SERIALNUMBER"

     

    for GSuite its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="SERIALNUMBER"
    • Like 3
    • Thanks 10
  9. Hi,

     

    du brauchst eine gültige Seriennummer für die Xpenology Installation sonst lässt sich die Lizenz nicht aktivieren. Bedenke: Wenn du eine zufällige Lizent nimmst die auch gültig ist, dann aktivierst du womöglich (nur eine Theorie) die Lizenz auch auf dem Besitzer seiner Synology-NAS mit genau der Seriennummer.

  10. The idea behind the recovery-method:

     

    1. You cant downgrade to 6.2 easily by just reinstalling the bootloader on the sdcard/usbstick. On every boot, the installed DSM 6.2.1 will update the bootloader for you
    2. To force a downgrade without another spare hdd, you have to change your Synology Model so the DSM installer will force a "clean install" instead of updating the bootloader

    Because of the reasons above you have to switch the bootloader von 3615 to 3617 or vice versa depending of what you have installed currently. So if you have DS3615 you have to flash the sdcard/usbstick with DS3617 so youll get into the recovery mode on the next boot.

     

    1. Leave all hdds as they are
    2. Take out the sdcard/usbstick on which the bootloader is installed and flash DS3617 from jun onto it
    3. Insert sdcard/usbstick and boot
    4. Youll get the "install dsm" screen which can be found with the synology assistent (just like you did when you first installed xpenology)
    5. Install the DSM 6.2 for DS3617 by "manual install" https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3617xs_23739.pat
    6. Optional: If you want to go back to DS3615
      1. Repeat steps above but flash DS3615 bootloader onto scdard/usbstick
      2. Install DSM 6.2 for DS3615 https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3615xs_23739.pat

    I guess thats detailed enough

    • Thanks 2
×
×
  • Create New...