Welcome to the Ajenti Idea Exchange. It's your chance to collaborate with our team and other users to influence the future of Ajenti! Ideas appreciated.

  1. Forum: General
+1
Fixed

Nginx plugin missing on CentOS 6.4

Ros vor 11 Jahren • aktualisiert von Eugene Pankov (Project coordinator) vor 11 Jahren • 4
I have installed Ajenti on CentOS 6.4, but I cannot see Nginx in Software sidebar.

Plugins page doesn't show a dependency unsatisfied warning.

I've tried
nginx-1.0.15-5.el6.x86_64
nginx-1.4.2-1.el6.ngx
ajenti.noarch 0:0.99.33-1
ajenti.noarch 0:0.99.34-1

Need your help :)
Antwort
Eugene Pankov (Project coordinator) vor 11 Jahren

Support for /etc/nginx/conf.d added to code

+1

How to run ajenti after successfully installing it through "pip2 install ajenti" in arch linux?

Tung Wai Fung vor 9 Jahren • 0
As stated in topic.
+1
Fixed

"Internal Server Error" on https://<ip-address>:8000

Mark De Jong vor 11 Jahren • aktualisiert von Eugene Pankov (Project coordinator) vor 11 Jahren • 0

I installed Ajenti on CentOS 6.4 64bit as instructed, but I can't login or even get a login screen. All I get is a white page with "Internal Server Error".


When I start with "ajenti-panel -v" in ssh it all looks ok except for the following error:

"ERROR SSL tunnel failed to start"


I got a same issue as a previous issue filed here: http://ajenti.userecho.com/topic/202435-this-webpage-is-not-available


Below the full log of running it with the stunnel test provided by Eugeny (https://gist.github.com/Eugeny/6038158).




[root@dappervps1 ~]# stunnel /tmp/stunnel.conf
2013.08.04 21:07:28 LOG5[1199:140560269387712]: stunnel 4.29 on x86_64-redhat-linux-gnu with OpenSSL 1.0.0-fips 29 Mar 2010
2013.08.04 21:07:28 LOG5[1199:140560269387712]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP
2013.08.04 21:07:28 LOG5[1199:140560269387712]: 500 clients allowed
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52507
2013.08.04 21:07:37 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35719
2013.08.04 21:07:37 LOG5[1199:140560269383424]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52506
2013.08.04 21:07:37 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35720
2013.08.04 21:07:37 LOG5[1199:140560269383424]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52509
2013.08.04 21:07:37 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35721
2013.08.04 21:07:37 LOG5[1199:140560269383424]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52508
2013.08.04 21:07:37 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:37 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35722
2013.08.04 21:07:37 LOG5[1199:140560269383424]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket
2013.08.04 21:07:39 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52510
2013.08.04 21:07:39 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:39 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35723
2013.08.04 21:07:40 LOG5[1199:140560269383424]: Connection closed: 161 bytes sent to SSL, 469 bytes sent to socket
2013.08.04 21:07:40 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52511
2013.08.04 21:07:40 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:40 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35724
2013.08.04 21:07:40 LOG5[1199:140560269383424]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket
2013.08.04 21:07:40 LOG5[1199:140560269383424]: default accepted connection from 12.34.56.789:52512
2013.08.04 21:07:40 LOG5[1199:140560269383424]: connect_blocking: connected 127.0.0.1:8000
2013.08.04 21:07:40 LOG5[1199:140560269383424]: default connected remote server from 127.0.0.1:35725
2013.08.04 21:07:40 LOG5[1199:140560269383424]: Connection closed: 161 bytes sent to SSL, 420 bytes sent to socket
Antwort
Eugene Pankov (Project coordinator) vor 11 Jahren
Fix released
+1

Ajenti has issues booting on new debian installation

Anthony 'Runt' Cleaves vor 9 Jahren • aktualisiert von Shillem Volpato vor 9 Jahren • 2

So I have got a fresh debian install usinga digitalocean VPS.


I have followed the installation tips here:


http://support.ajenti.org/topic/349864-installing-on-debian/


I am unable to browse to my website, at first I noticed the port was bound to 0:0:0:0, so I changed that to my servers IP in the config and restarted the service. This did not fix the issue, I am seeing this error in the logs. (Nothing was installed on this VPS prior to Ajenti installtion)


Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/gevent/greenlet.py", line 327, in run
result = self._run(*self.args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/gevent/server.py", line 102, in wrap_socket_and_handle
ssl_socket = self.wrap_socket(client_socket, **self.ssl_args)
File "/usr/lib/python2.7/dist-packages/gevent/ssl.py", line 382, in wrap_socket
ciphers=ciphers)
File "/usr/lib/python2.7/dist-packages/gevent/ssl.py", line 84, in __init__
ctx = SSLContext(ssl_version)
NameError: global name 'SSLContext' is not defined
<Greenlet at 0x7fc1a530cd70: <bound method SocketIOServer.wrap_socket_and_handle of <SocketIOServer at 0x7fc1a4d8c0d0 fileno=8 address=46.101.75.44:8000>>(<socket at 0x7fc1a5301f10 fileno=11 sock=46.101.75, ('213.138.113.36', 50579))> failed with NameError

+1
Abgelehnt

I hope you will support a gentoo ebuild soon

Neo Futur vor 11 Jahren • aktualisiert von Eugene Pankov (Project coordinator) vor 11 Jahren • 0
would be great to emerge ajenti on gentoo !


Antwort
Eugene Pankov (Project coordinator) vor 11 Jahren

As much as I regret to say this, Gentoo will not be supported anytime soon, and probably never due to being the least used (<0.5% for 0.6.x) Ajenti platform and one of the hardest to maintain

+1

This webpage is not available

Mailfancy vor 9 Jahren • aktualisiert von Jeremy Henry vor 9 Jahren • 1
I am trieng rto open my server backend but is not fount.

this is ip link: https://176.58.127.193:8000/


please sloved this issue
+1

Ajenti Terminal plugin ability to stay tuned after logout

Vaidas vor 9 Jahren • 0
+1

[REQUEST] pure-ftpd custom configuration

ReckeDJ vor 9 Jahren • 0
Hi all,

It would be nice if we can change the default pure-ftpd configuration.
As described in: http://support.ajenti.org/topic/621403-pure-ftpd-passive-mode-fail/ there is a way of doing this by editing the plugin scripts, but of course, when there is an update for the plugin, it will override my custom settings.
So, I suggest to add an extra configuration field in Configura > Plugins > PureFTPD.


Just an idea?


Thanks in advance, I just started to use Ajenti, and I am really impressed.
Greetz,
Joey
+1
Fertiggestellt

Same account for mailbox and forwarding

Sorin Gitlan vor 10 Jahren • aktualisiert vor 10 Jahren • 5
There is an option in cPanel and Virtualmin (maybe in others also) where you could
create a mailbox and a forwarding for the same account.

Example:
All mail sent to test@example.com is saved into that mailbox but it is also
forwarded to another email account like testing@gmail.com 

This would be a very useful function for those who want to keep a backup for the received emails
but use Gmail for example to aggregate multiple email accounts.




Customer support service by UserEcho