Troubleshooting Spaces

Resolve connection problems and configuration issues with this comprehensive troubleshooting guide. Find solutions for the most common space-related problems.

Connection failures

”Connection refused”

The server is not accepting connections on the specified port.

Diagnostic steps:

# Test if port is open
nc -zv hostname 22
telnet hostname 22

# Check if SSH is running
sudo systemctl status sshd
sudo netstat -tlnp | grep :22

Common causes:

• SSH service not running
• Firewall blocking port
• Wrong port specified
• Server not reachable

Solutions:

1. Start SSH service: sudo systemctl start sshd
2. Check firewall: sudo ufw allow 22
3. Verify port in /etc/ssh/sshd_config
4. Test with: ssh -v user@host

”Network unreachable”

Cannot establish network path to server.

Diagnostic steps:

# Test network connectivity
ping hostname
traceroute hostname
nslookup hostname
ip route get hostname

Common causes:

• No internet connection
• VPN disconnected
• Wrong network
• DNS resolution failure

Solutions:

1. Check Wi-Fi/cellular connection
2. Connect to required VPN
3. Verify hostname/IP address
4. Try IP instead of hostname

”Connection timeout”

Connection attempt takes too long and fails.

Common causes:

• Firewall dropping packets
• Server overloaded
• Network congestion
• Incorrect IP address

Solutions:

1. Try different network
2. Check server status
3. Use alternative port
4. Increase timeout value

Authentication problems

”Permission denied”

Authentication failed with provided credentials.

Diagnostic steps:

# Verbose SSH connection
ssh -vvv user@host

# Check auth methods
ssh -o PreferredAuthentications=none user@host

# View auth log (on server)
sudo tail -f /var/log/auth.log

Password authentication:

• Verify username spelling
• Check password accuracy
• Confirm caps lock is off
• Try copy/paste password

Account issues:

• Verify account is active
• Check SSH access enabled
• Confirm user in AllowUsers
• Try sudo access if available

”No supported authentication methods”

Server doesn’t accept password authentication.

Common causes:

• Password auth disabled on server
• Account locked
• SSH not properly configured
• Server misconfiguration

Solutions:

1. Check server config:

   /etc/ssh/sshd_config

   PasswordAuthentication yes

2. Restart SSH service:

   sudo systemctl restart sshd

3. Contact server administrator

”Host key verification failed”

Server’s identity cannot be verified.

Causes:

• First connection to server
• Server reinstalled
• Possible security issue
• Changed server key

Safe resolution:

1. Verify with administrator
2. Remove old key:

   ssh-keygen -R hostname

3. Accept new key on next connection

Performance issues

Slow connections

Connection established but very slow.

Diagnostic tools:

# Test latency
ping -c 10 hostname

# Check bandwidth
speedtest-cli

# Monitor connection
mtr hostname

Solutions:

1. Enable compression:

   # In Kisuke space settings
   Compression: yes

2. Use faster cipher:

   Ciphers aes128-ctr

3. Try different network
4. Check server load

Frequent disconnections

Connection drops unexpectedly.

Common causes:

• Unstable network
• Idle timeout
• Server killing idle connections
• Power saving features

Solutions:

1. Enable keepalive:

   ServerAliveInterval 60
   ServerAliveCountMax 3

2. Disable power saving
3. Use more stable network
4. Consider using tmux/screen

Configuration issues

Space won’t save

Cannot save space configuration.

Possible causes:

• Storage full
• Permission issues
• Invalid configuration
• App needs update

Solutions:

1. Check device storage
2. Reinstall app
3. Verify all fields filled
4. Update to latest version

Settings not applying

Changes don’t take effect.

Solutions:

1. Disconnect and reconnect
2. Force close and reopen app
3. Check for typos in settings
4. Delete and recreate space

Network-specific issues

Behind corporate firewall

Cannot connect from work network.

Solutions:

1. Use approved VPN
2. Try port 443 (HTTPS)
3. Configure proxy settings
4. Use jump host

Hotel/public Wi-Fi

Restricted network access.

Solutions:

1. Accept captive portal
2. Use VPN service
3. Try alternative ports
4. Use mobile hotspot

Mobile network issues

Cellular connection problems.

Solutions:

1. Check data allowance
2. Disable low data mode
3. Try different location
4. Switch to Wi-Fi

Advanced diagnostics

Debug logging

Enable verbose output:

In Kisuke:

• Settings → Advanced → Debug Mode

SSH command line:

ssh -vvv user@host

Connection testing

Test each component:

# DNS resolution
nslookup hostname

# Network path
traceroute hostname

# Port accessibility
nc -zv hostname 22

# SSH handshake
ssh -v -o ConnectTimeout=5 user@host

Server-side checks

Verify server configuration:

# SSH daemon status
sudo systemctl status sshd

# Active connections
sudo ss -tlnp | grep :22

# Firewall rules
sudo iptables -L -n

# Auth logs
sudo journalctl -u sshd -f

Getting help

Information to collect

When seeking help, provide:

1. Exact error message
2. Connection details (hide passwords)
3. Network type (Wi-Fi/cellular/VPN)
4. iOS and Kisuke versions
5. What changed recently

Debug information

Export diagnostic data:

1. Settings → Support → Export Logs
2. Include connection attempts
3. Sanitize sensitive data
4. Share with support

Community resources

Get help from:

• GitHub Issues
• User forums
• Documentation
• Support email

Prevention tips

Regular maintenance

• Test connections periodically
• Update credentials before expiry
• Monitor server health
• Keep app updated

Backup strategies

• Export space configurations
• Document server settings
• Test restore procedures
• Multiple auth methods

Next steps

• Network configuration →
• Security hardening →
• Performance optimization →

Tip

Most connection issues are caused by network configuration or firewall rules. Always verify basic connectivity with ping and check if the SSH port is accessible before investigating other causes.