Access via SSH
In order to troubleshoot accurately and most efficiently, I would need SSH access to your server(s).
I understand there are risks involved in giving me direct access and some regulations or certifications will not allow for this. If SSH access is not possible, I will re-create your environment locally (your OS + software), but it will take more time.
If you restrict SSH access to a limited amount of IPs (good!), you can give access to IPv4
220.127.116.11 or IPv6
SSH Public Key
Please add my public key to your SSH server configuration.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCiFuEpiskdQ8Ku2xN4nwc6W7CDDnVLxKAB9TQT/vmnlcNbVZ6xZvbK9Q81Uo8cLVDp8NV0AfOK/suiUgNKGI0C3ifT533YsJW+Qj0Y2cNLTEfDCN00gQJfq0tdDwmNiRATCpDJyAP4GUQkmfBxsO/G3QAlgs2JuzNSD4xmhvsAs/EwV9+udPPsjoD/d82zE8drLrXwwLPAxtn7gUADYLEh2hroSdKsgrIH1REO2mNbfPl096u2rtjYCT0OGb4hztKpdijCaLXEkypb8J77ikhLcyOEBD6esJk3n0w9G6MKYvxRirwNdHrP+70pC5yinm2DeG4jKVkfhPboLs6NZnv5 mattias@mbp
Permissions on your server
I would most likely need root level permissions to troubleshoot and debug. If you grant me access via non-privileged account, please allow me to escalate my privileges using
If a password is required to use
sudo, you can create a text-file in my home directory on your server with the password in it.