Jump to content
Vodia PBX forum

mikeboss

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikeboss

  • Rank
    Member
  1. switched on "SSH access" in the web GUI and rebooted the Raspberry Pi. now I can see on the Raspberry's screen: FAILED to start OpenBSD Secure Shell server. I mean, it's no biggie for me. since I do have a screen and a keyboard attached to the system, I can install dropbear (which works with 62.1). but for others this might be a problem...
  2. yes, as stated above: 62.1 (Build Date: Apr 11 2019 17:13:20)
  3. did a fresh install of the latest Raspbian (2019-04-08-raspbian-stretch-lite.img) same procedure: installed 62.0 then updated to 62.1 using the web GUI. did a reboot and afterwards -> SSH connection refused.
  4. oh, there's a new Raspbian release from a few days ago. will try that, too.
  5. nope, still the same: SSH connection refused after update 62.0 -> 62.1
  6. I'm pretty sure I did a reboot... okay, will start from scratch. fresh install again. back in a few minutes.
  7. hm, also hier immer noch das gleiche... jungraeuliches Raspbian auf Raspberry Pi 3 Model B+ Vodia Release 62.0 gemaess anleitung installiert SSH OK update via web GUI auf 62.1 (Build Date: Apr 11 2019 17:13:20) durchgefuehrt SSH Connection refused
  8. der fehler besteht nach wie vor: Software-Version: 62.1 (Vodia mini PBX (Debian)) Build Date: Apr 8 2019 14:22:24 (Raspbian Stretch und anschiessend Vodia 62.1 frisch installiert)
  9. aktuell bekomme ich beim installieren 62.1 (Vodia mini PBX (Debian)) Build Date Mar 25 2019 13:54:39 ich habe jetzt mal openssh-server deinstalliert und nutze stattdessen Dropbear SSH, das funktioniert.
  10. I can confirm that this is fixed (release 62.1 build date Mar 29 2019 15:49:34)
  11. okay, I tried it again (on a virtual machine this time). freshly installed debian stretch 64 bit. edited "install-debian.sh" so it'll download release 62.1 and installed it according to the manual. login to the web GUI, set a new password for the PBX, logged out -> unable to login with the new password, logging in without password is still possible.
  12. isn't the version downloaded during install the same as the one from the update? I installed 62.1 without updating it, this was today in the morning (march 29th).
  13. soll ich fehler betreffend 62.1 ueberhaupt melden? frische installation von 62.1 (mittels angepasstem install-debian.sh) auf debian64 lizenz installiert wenn ich in der web GUI das admin passwort anpasse und speichere greift die einstellung nicht. mit dem neu konfigurierten passwort kann man sich hinterher nicht anmelden, ohne passwort hingegen schon. fehler tritt auf release 62.0 (erneut frisch installiert auf debian64) nicht auf.
  14. von einem frisch aufgespielten Raspbian Stretch (2018-11-13-raspbian-stretch-lite.img) /lib/systemd/system/ssh.service [Unit] Description=OpenBSD Secure Shell server After=network.target auditd.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Service] EnvironmentFile=-/etc/default/ssh ExecStartPre=/usr/sbin/sshd -t ExecStart=/usr/sbin/sshd -D $SSHD_OPTS ExecReload=/usr/sbin/sshd -t ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartPreventExitStatus=255 Type=notify [Install] WantedBy=multi-user.target Alias=sshd.service /etc/ssh/sshd_config wobei ich da eh ueblicherweise "PermitRootLogin yes" einstelle # $OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options override the # default value. #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_ecdsa_key #HostKey /etc/ssh/ssh_host_ed25519_key # Ciphers and keying #RekeyLimit default none # Logging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin prohibit-password #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 #PubkeyAuthentication yes # Expect .ssh/authorized_keys2 to be disregarded by default in future. #AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2 #AuthorizedPrincipalsFile none #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no # Change to yes to enable challenge-response passwords (beware issues with # some PAM modules and threads) ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes #GSSAPIStrictAcceptorCheck yes #GSSAPIKeyExchange no # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. UsePAM yes #AllowAgentForwarding yes #AllowTcpForwarding yes #GatewayPorts no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes PrintMotd no #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation sandbox #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS no #PidFile /var/run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none # no default banner path #Banner none # Allow client to pass locale environment variables AcceptEnv LANG LC_* # override default of no subsystems Subsystem sftp /usr/lib/openssh/sftp-server # Example of overriding settings on a per-user basis #Match User anoncvs # X11Forwarding no # AllowTcpForwarding no # PermitTTY no # ForceCommand cvs server
  15. release 62.1 direkt auf einem frischen Raspbian Jessie (anstelle Stretch) installiert und alles funktioniert wie es soll. benutztes image: 2017-07-05-raspbian-jessie-lite.img Raspbian Jessie bootet aber leider nicht mehr auf den neuen Raspberry Pi 3 Model B+
×
×
  • Create New...