Hey everyone,

I have this server installed for a few years now, after COVID 19 pandemic we went back to the office and found our VM was off. We restarted it, and now we can get emails re routed from the server to our Google inboxes, however, we are not able to access the web interface as we used to.
Investigating on the server, it looks like the httpd.service cannot be started as there are other services already running on port 80.

Can you guys help me troubleshoot and solve this problem? I would like to have the web interface back again 🙁

EDIT: Im really not sure what version I'm using as I cannot access the web service. Any CLI that might help on that?
I tried SELECT ostversion FROM ost_config; but it did not work.

@Erudes

This has nothing to do with osTicket rather your VM setup. It's saying something else is running on port 80 so it cannot start Apache. Port 80 is typically used to serve unencrypted web traffic (HTTP) via the webserver (in your case Apache). Since something else is using that port Apache cannot bind to it. You will need to run something like netstat -tuplen to see the running processes and see what's running on port 80. You can then determine wether to kill that service and quickly start Apache so it can bind to the port OR you can configure Apache to serve on a different port than 80. Of course all of this is outside the scope of the osTicket software.

Cheers.

Well since you mention httpd I presume that you are running Apache, but what OS are you running?

It sounds like you are going to have to figure out what is running on port 80 and kill it.

To determine that version of osTicket that you are running you can look at the bootstrap.php and search for THIS_VERSION and it will tell you what version you are running (assuming the you are running a contemporary version).

Write a Reply...