Resolved SSH and Apache Port Conflict on Server

2 min read

Resolved SSH and Apache Port Conflict on Server

  • Day: 2024-09-14
  • Time: 18:35 to 18:45
  • Project: Dev
  • Workspace: WP 2: Operational
  • Status: Completed
  • Priority: MEDIUM
  • Assignee: Matías Nehuen Iglesias
  • Tags: SSH, Apache, Configuration, Troubleshooting, Web Services

Description

Session Goal

The primary goal of this session was to resolve a server misconfiguration issue where SSH was incorrectly set to listen on port 80, which is reserved for Apache, causing web service failures.

Key Activities

  • Troubleshooting SSH and Apache Configuration: Detailed steps were followed to verify Apache configurations and resolve the port conflict by ensuring SSH listens on the correct port.
  • Technical Documentation: A technical memo was created to outline the steps for resolving the website issue caused by the port misconfiguration.
  • SSH Connection Setup: Provided essential connection details for server access via SSH, including IP address, port, and username.
  • Service Verification: Restarted the SSH service and verified it was listening on the correct port (65432), including ensuring the port was open.
  • Remote Access Guide: Developed a guide for connecting to remote machines using SSH through AWS EC2, Google Cloud, and other providers, including troubleshooting tips.

Achievements

  • Successfully resolved the port conflict between SSH and Apache, restoring web service functionality.
  • Created comprehensive technical documentation for future reference.
  • Ensured SSH service was correctly configured and accessible on the designated port.

Pending Tasks

No pending tasks remain as the session objectives were fully achieved.

Evidence

  • source_file=2024-09-14.sessions.jsonl, line_number=5, event_count=0, session_id=10d5269f143e462d70dc81a4680e3c313f708522607d647f618bc328848f94eb
  • event_ids: []

Graph View

Backlinks