Title: Array offset error line 263
Last modified: April 12, 2024

---

# Array offset error line 263

 *  Resolved [Leif Harmsen](https://wordpress.org/support/users/leifharmsen/)
 * (@leifharmsen)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/array-offset-error-line-263/)
 * PHP Warning: Trying to access array offset on value of type bool in /var/www/
   historicwoodfield.ca/html/wp-content/plugins/ssh-sftp-updater-support/class-wp-
   filesystem-ssh2.php on line 263, referer: [https://historicwoodfield.ca/wp-admin/update-core.php](https://historicwoodfield.ca/wp-admin/update-core.php)
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Farray-offset-error-line-263%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Author [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * (@davidanderson)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/array-offset-error-line-263/#post-17688696)
 * You’ll see this PHP notice if no successful connection could be made to your 
   SSH/SFTP server.

Viewing 1 replies (of 1 total)

The topic ‘Array offset error line 263’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/ssh-sftp-updater-support.svg)
 * [SSH SFTP Updater Support](https://wordpress.org/plugins/ssh-sftp-updater-support/)
 * [Support Threads](https://wordpress.org/support/plugin/ssh-sftp-updater-support/)
 * [Active Topics](https://wordpress.org/support/plugin/ssh-sftp-updater-support/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ssh-sftp-updater-support/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ssh-sftp-updater-support/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * Last activity: [2 years, 1 month ago](https://wordpress.org/support/topic/array-offset-error-line-263/#post-17688696)
 * Status: resolved