Cannot access Ajenti on port 8000 / General форум / Ajenti

Оглавление:

1 Ответ
2 Ответы 31

Статья последний раз была обновлена 04.03.2023

General
Вопросы

ОТКЛОНЕН

Tiny Nas 2 года назад • обновлен Luke van der Palen 2 недели назад • 31

I’m running Apache 2 on Raspbian and even though Ajenti installed and is running I cannot access it on the default port as my browser says there isn’t anything to be displayed.

Голос

2 1

Ответ

Eugene Pankov (Project coordinator) 2 года назад

Ответы 31
Старые сверху

Eugene Pankov (Project coordinator) 2 года назад

Does Apache take up the port 8000? You can check that by running:

sudo netstat -tlnp | grep 8000

If so, you can either reconfigure Apache (ports.conf) to use different port or change Ajenti port in /etc/ajenti/config.json

Ответить

Erik Nasaroff 2 года назад

For anyone else having the same problem:

make sure you’re trying to access it via https

Maybe the http page could be made to redirect to the https one.

Ответить

ОТВЕТ

ОТКЛОНЕН

Eugene Pankov (Project coordinator) 2 года назад

Ответить

Berriotxoa Torresagasti 1 год назад

I have the same problem. Everything worked well during installation and after that for some time. I could login and everything.

However, I set the server aside for a while and didn’t use it. When I tried to login again, port 8000 was not available. The webserver is still running, as well as the applications, it is just not possible to access the Ajenti panel anymore.

Tried "sudo netstat -tlnp | grep 8000" and it did… nothing.

Access is tried with https.

Not sure what happened.

Ответить

Berriotxoa Torresagasti 1 год назад

Problem solved. An update / upgrade process solved the issue. No idea why but it did.

Ответить

Viraj Patel 1 год назад

I am having same problem

tried update and upgrade no luck

Ответить

Daman Mokha 12 месяцев назад

I am also having same problem can not open panel. opening with https and also allowed the port

Ответить

Leonardo Martinez 11 месяцев назад

The same here.. is was working fine for few days and now i can’t access to ajenti panel but is running

Ответить

Eugene Pankov (Project coordinator) 11 месяцев назад

Please follow the troubleshooting guide http://support.ajenti.org/topic/507352-troubleshooting/

Ответить

Leonardo Martinez 11 месяцев назад

I’ll post my results here, thank you!

Ответить

Idso 8 месяцев назад

I have done all of the above suggestions, even tried changing the port to 9000, but I can not access ajenti on any port with https, nor with http.

I am running a fresh install of Ubuntu 14.10 with LAMP and OpenSSHserver; for the rest it is all standard.

During installation there were no errors.

Ответить

Pepijn Mulders 8 месяцев назад

Me Neither. Running CentOS 6 and did not install anything less then Ajenti, nginx, etc. Nothing is happening. Ajenti is running, no strange errors when running in foreground with: ajenti-panel -v

Nginx is running fine but cant see any login page with or without https.

Ответить

Idso 8 месяцев назад

I have given up on Ajenti and I am now running ISPConfig version 3. I can highly recommend it.

Ответить

German Franco Grisales 8 месяцев назад

Same here, have been trying for two weeks on CentOS 7, Centos 6.5 & CentOS 6.6.

In all of them the same issue, ajenti service running Ok, IPTables Ok (for tcp and udp), Port 8000 listening… Ajenti… never get to work on any browser with/without https.

Too bad, I was hopeful since I’ve heard in the past so many good things about it.

Moving now to CWP (Centos Web Panel).

Still will give the try on ISPConfig as recommended by Idso

Ответить

Daniel 7 месяцев назад

I´ve got the same problem, installation went well, but cant login on https or http. I´m running ubuntu 14.10 with apache2 installed.

i changed "enable ssl" from "true" to "false" in config.json and now im able to see the loginpanel. — So try that

It seems that something with ssl and apache2 needs to be changed.

Ответить

Th3gh0st 7 месяцев назад

I can confirmed that Daniels hot fix is working!

If we take a look in the config.json:

"bind": {

"host": "0.0.0.0",

"port": 8000

The host is 0.0.0.0? And just now I can´t see how the config.json are on my other 2 servers.

Ответить

Nikita Lyubchich 7 месяцев назад

I ran into the same problem yesterday and I found the real fix (without a risk of insecure connection) through upgrading gevent package with the next command:

pip install gevent --upgrade

In case of any troubles with upgrading, try to install its dependence:

aptitude install python-dev

Ответить

SeLoRe_28 7 месяцев назад

Nikita Lyubchich your fix is right but first run this

aptitude install python-dev

and after this

aptitude install python-dev

because giving error witout install python

Ответить

Vandalism 5 месяцев назад

This is the real fix. It needs to be added to main install script, because default recommendation is to use HTTPS connection. Thank you for the help

Ответить

Jaime Vásquez 4 месяца назад

Thanks Nikita, your fix it works for me.

Ответить

Psycho24 5 месяцев назад

Hi the combination of Nikitas and SeLoRe_28 commands helped me to get in Ajenti per https

First you have to follow SeLoRe’s commands and to install missing packages and then do the same with Nikitas. After 4 Hours of Searching i can now get in. Thank you .

Ответить

Spiltoir 5 месяцев назад

Hi all,

I had the same problem.

I have apache2 installed and ajenti (I follow the ajenti install steps from ajenti’s web site) and fresh Server ubuntu 14.04.

I’ve changed the

"bind": {

"host": "0.0.0.0",

"port": 8000

"bind": {

"host": "myServerIp",

"port": 8000

restarted ajenti service and it works.

Ответить

Acpmasquerade 5 месяцев назад

ufw allow 8000

That was exactly what made the server running. Didn’t notice that the ufw firewall was running in the server.

Ответить

Ryan 3 месяца назад

Hi,

While running Ajenti in debug mode:

ajenti-panel -v

I encountered the following error:

SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:581)

One of the Traceback calls referenced a line in the ssl.py file, which for me was found here (your path may vary):

/usr/local/lib/python2.7/dist-packages/gevent-1.0.1-py2.7-linux-x86_64.egg/gevent/ssl.py

In that file I navigated to this line:

def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None)

and changed it to:

def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv23, ca_certs=None)

Then ran:

service ajenti restart

Why? Well because as I understand it, newer versions of Debian (I’m on Jessie) or Ubuntu run the SSLv23 protocol whereas older libraries like gevent (even the latest I believe) are stuck on SSLv3. I believe this change was due to the poodle vulnerability.

Anyways there’s also a good chance I have no idea what I’m talking about but I thought I’d share what worked for me.

Cheers.

Ответить

Thomasrc 2 месяца назад

Same here. I am using Ajenti under Debian 8 (Jessie) too and I get the same error message, so I can confirm this. If I turn off the ssl, everything is OK.

Ответить

Jose R. Prieto 2 месяца назад

I’m agree with Ryan; same error, same solution.

But, is this a bug of the Ajenti package for Debian 8, or not?

I think that is a bug, and it’s neccesary to fix it.

It should be fixed on the repo:

deb http://repo.ajenti.org/debian main main debian

Ответить

Patryk Padus 2 месяца назад

This error occur which clean install and "ssl" -> enabled : true

No solution found.

"SSL Content" error and etc occur in debug start.

For now SSL is False and work fine.

Big thanks for all support.

In short:

Debian 8.1 / OVH Classic / Fresh install / No connection (no panel) when go to httpS://website.com:8000 / Work fine witchout ssl

Ответить

Axtux 4 недели назад

Easy fix from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766867

Edit file /usr/lib/python2.7/dist-packages/gevent/ssl.py on line 84 :

-            ctx = SSLContext(ssl_version)
+            ctx = __ssl__.SSLContext(ssl_version)

Ответить

Seth M Rainsdon 3 недели назад

This worked for me on two servers running Ubuntu 15.04 Thanks Axtux

Ответить

Anton Staroverov 3 недели назад

Solution from @Axtux worked for me too (Debian 8)!

Ответить

Luke van der Palen 2 недели назад

Having the same issues running it on EC2 with port 8000 opened through security groups. Unfortunately the patch is currently not working anymore because ssl.py is updated to a newer version. Strange enough when changing the port to 80 and disabling the default nginx config, i can acces it through http, but i’m almost 100% sure the ports are opened.

Update: a port check confirms port 8000 is open. Still Ajenti is unable to bind to ‘0.0.0.0’, 8000

Ответить

http://support.ajenti.org/topic/201136-cannot-access-ajenti-on-port-8000/

Об авторе
Недавние публикации

Губарь Маргарита Александровна

Кандидат технических наук, доцент кафедры ИУ-6 (Компьютерные системы и сети) Московского государственного технического университета им. Н. Э. Баумана. Самый молодой в России PhD in Computer Science. Эксперт в области компьютерных технологий и программирования.

Стаж: 8 лет.

Образование: МГТУ им. Н. Э. Баумана, к.т.н.

Моя кафедра

Губарь Маргарита Александровна недавно публиковал (посмотреть все)

Рубрика: Linux | Метка: Веб-панель Ajenti

Чтобы найти

Чтобы не потерять

От большого

Cannot access Ajenti on port 8000 / General форум / Ajenti

Ответ

Ответы 31

Чтобы найти

Чтобы не потерять

От большого

К малому

Cannot access Ajenti on port 8000 / General форум / Ajenti

Ответ

Ответы 31