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.
No similar topics found.
0
cant access ajenti from just my pc
So i have a 1:1 NAT set up for my server with ajenti, i have apache set up to a port i want no issus and can access it via my fqdn:port however no matter what i do i cannot get ajenti to be outside world accessible, only by the internal ip. so i changed the hostname for ajenti from 0.0.0.0 to my fqdn and now i cant access ajenti. i even changed it back to 0.0.0.0 and restarted from ssh but i cannot open ajenti i get "Page could not be displayed". however i can access ajenti even after the ip change on any other computer but mine. the only way to fix this issue is to completely restart the server. different web browsers cant access it either. changing my pc's local ip doesnt make a difference, clearing cache and cookies makes not difference. no matter what i do it wont work until i completely reboot the server. oh and i still cant connect via https://fqdn:8000. i can however connect to http://fqdn:8000 if i turn ssl off however after logging in i get the ajenti bar up top and an empty page with no control panel on it. so really i have 2 issues here. 1 appears to be some kind of bug or glitch the other is maybe my configuration jacked up? i dont know. ive set up ajenti on a dozen VPSs for clients and have never had even 1 issue and now im just trying to set it up on 1 local server and i have had nothing but problem after problem.
0
Not a bug
CLI wbesite Import - 500 Error
I always get an:
500 Errorwhen trying to import a previosly exported JSON file.
Config does not exist
Answer
Eugene Pankov (Project coordinator)
10 years ago
You need to use an absolute path to the file.
0
The Night Light is very cool :o)
I use Ajenti 2 weeks now and tonight i found the night light at the bottom right area.
Its sooo cool.
Thanks for the nice work!
Its sooo cool.
Thanks for the nice work!
0
Fixed
не работает панель
обновил с версии 0.6.3 и ajenti перестал работать. Команда service ajenti restart работает, но сайт не открывается дебаг выдал:
30.08.2013 09:17 ajenti-panel:81 INFO Ajenti starting in foreground
30.08.2013 09:17 registry.py:247 INFO registered crypt handler 'sha512_crypt': <class 'passlib.handlers.sha2_crypt.sha512_crypt'>
30.08.2013 09:17 core.py:95 INFO Ajenti 1.0.3 running on platform: debian
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin plugins
30.08.2013 09:17 __init__.py:249 DEBUG Preloading plugin dependency: main
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin main
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin plugins
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin raid
30.08.2013 09:17 __init__.py:309 WARN *** [raid] skipping due to BinaryDependency (mdadm)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin terminal
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin services
30.08.2013 09:17 __init__.py:249 DEBUG Preloading plugin dependency: dashboard
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin dashboard
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin services
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin vh
30.08.2013 09:17 __init__.py:303 WARN *** [vh] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin network
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin memcache
30.08.2013 09:17 __init__.py:309 WARN *** [memcache] skipping due to BinaryDependency (memcached)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin sensors
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin scripts
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin apache
30.08.2013 09:17 __init__.py:249 DEBUG Preloading plugin dependency: webserver_common
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin webserver_common
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin apache
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin ajenti_org
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin netatalk
30.08.2013 09:17 __init__.py:309 WARN *** [netatalk] skipping due to BinaryDependency (afpd)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin bind9
30.08.2013 09:17 __init__.py:309 WARN *** [bind9] skipping due to BinaryDependency (named)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin elements
30.08.2013 09:17 __init__.py:303 WARN *** [elements] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin samba
30.08.2013 09:17 __init__.py:309 WARN *** [samba] skipping due to BinaryDependency (smbd)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin openvpn
30.08.2013 09:17 __init__.py:309 WARN *** [openvpn] skipping due to BinaryDependency (openvpn)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin squid
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin mysql
30.08.2013 09:17 __init__.py:249 DEBUG Preloading plugin dependency: db_common
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin db_common
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin mysql
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin logs
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin configurator
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin supervisor
30.08.2013 09:17 __init__.py:309 WARN *** [supervisor] skipping due to BinaryDependency (supervisord)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin nginx
30.08.2013 09:17 __init__.py:309 WARN *** [nginx] skipping due to BinaryDependency (nginx)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin codemirror
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin packages
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin hosts
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin users
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin resources
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin dhcpd
30.08.2013 09:17 __init__.py:309 WARN *** [dhcpd] skipping due to BinaryDependency (dhcpd)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin cron
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin ctdb
30.08.2013 09:17 __init__.py:309 WARN *** [ctdb] skipping due to BinaryDependency (ctdb)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin nsd
30.08.2013 09:17 __init__.py:309 WARN *** [nsd] skipping due to BinaryDependency (nsd)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin notepad
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin fstab
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin exports
30.08.2013 09:17 __init__.py:309 WARN *** [exports] skipping due to BinaryDependency (nfsstat)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin psql
30.08.2013 09:17 __init__.py:309 WARN *** [psql] skipping due to BinaryDependency (psql)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin power
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin munin
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin iptables
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin taskmgr
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin resolv
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin lm-sensors
30.08.2013 09:17 __init__.py:309 WARN *** [lm-sensors] skipping due to BinaryDependency (sensors)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin fm
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin megaraid
30.08.2013 09:17 __init__.py:309 WARN *** [megaraid] skipping due to FileDependency (/opt/MegaRAID/MegaCli/MegaCli)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin smartctl
30.08.2013 09:17 __init__.py:309 WARN *** [smartctl] skipping due to BinaryDependency (smartctl)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin hddtemp
30.08.2013 09:17 __init__.py:309 WARN *** [hddtemp] skipping due to BinaryDependency (hddtemp)
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin pkgman
30.08.2013 09:17 __init__.py:303 WARN *** [pkgman] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin hddstat
30.08.2013 09:17 __init__.py:303 WARN *** [hddstat] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin sysload
30.08.2013 09:17 __init__.py:303 WARN *** [sysload] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin shell
30.08.2013 09:17 __init__.py:303 WARN *** [shell] Plugin error: format error
30.08.2013 09:17 __init__.py:260 DEBUG Loading plugin filesystems
30.08.2013 09:17 __init__.py:303 WARN *** [filesystems] Plugin error: format error
30.08.2013 09:17 core.py:39 INFO Starting SSL tunnel for port 59225
30.08.2013 09:17 core.py:118 ERROR SSL tunnel failed to start
30.08.2013 09:17 core.py:123 INFO Starting server on (u'192.168.10.10', 8082)
Activating emergency console
----------------------------
Caused by:
error
Stack frames:
[ 0] /usr/bin/ajenti-panel:86
[ 1] /usr/lib/pymodules/python2.7/ajenti/core.py:133
listener.bind(bind_spec)
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/exconsole/console.py", line 22, in handle_exception
launch(exception=value, extraceback=tb)
File "/usr/lib/pymodules/python2.7/exconsole/console.py", line 130, in launch
_cmd_stack()
File "/usr/lib/pymodules/python2.7/exconsole/console.py", line 77, in _cmd_stack
lines, current_line = inspect.getsourcelines(frame)
File "/usr/lib/python2.7/inspect.py", line 690, in getsourcelines
lines, lnum = findsource(object)
File "/usr/lib/python2.7/inspect.py", line 538, in findsource
raise IOError('could not get source code')
IOError: could not get source code
Original exception was:
Traceback (most recent call last):
File "/usr/bin/ajenti-panel", line 84, in <module>
core.run()
File "/usr/lib/pymodules/python2.7/ajenti/core.py", line 133, in run
listener.bind(bind_spec)
File "<string>", line 1, in bind
socket.error: [Errno 98] Address already in use
0
Fixed
Install Ajenti 1.0.8 on Debian Wheezy
I'm trying to install ajenti in my server machine.
using apt-get install ajenti I get this error
Setting up ajenti (1.0.8) ...
update-rc.d: error: unable to read /etc/init.d/ajenti
Traceback (most recent call last):
File "/usr/bin/ajenti-ssl-gen", line 17, in <module>
conf = json.loads(open(config_path).read())
IOError: [Errno 2] No such file or directory: '/etc/ajenti/config.json'
Something got broken?
0
Answered
ssh/ Authorized Keys
Working inside Ajenti V for a couple days getting familiarized. I don't know if it's when I added users or changed a password, but logging into cli or sftp (winSCP) stopped me from using the .ppk file and just requires a password (server refused our key). At first I thought I was locked out but then tried the passwords and they worked. Not generally what I would like to leave open. Is this a requirement of using Ajenti if you're setting up websites? thx for a great software, Stu
Answer
Eugene Pankov (Project coordinator)
11 years ago
Hi Stu,
Ajenti doesn't affect your ability to use SSH pubkey auth. However, if you deleted and recreated user, it's possible that their authorized_keys file was lost. Try looking for the <user home>/.ssh/authorized_keys file and checking whether your public key is present there.
Ajenti doesn't affect your ability to use SSH pubkey auth. However, if you deleted and recreated user, it's possible that their authorized_keys file was lost. Try looking for the <user home>/.ssh/authorized_keys file and checking whether your public key is present there.
0
Any domain name give 403
I have installed new vagrant box with ubuntu 14.04, than i installed Ajenti. After that i installed Ajentiv-V using manual on this site. I have created new website (BTW was doing that a lot with ajenti-v before) remove "Maintaince mode" checkbox. Created directory for new website, created domain name, created PHP FastCGI in content tab.
Than i restart websites.
All that actions i made through https on my VM throught ajenti web interface
On my host machine i mde change to redirect mywebsite.dev to proper ip adress where ajenti is, and than i have issue with 403 permission.
So i can't get to any website due the 403 permission.
I have no errors in nginx .log.
I was doing that a lot of times before and i have no issue before. But now i change my host machine from windows to ubuntu, i don't think this is the reason of issue.
Please help.
Answer
Eugene Pankov (Project coordinator)
10 years ago
Just with anything else, you can use MariaDB as a drop-in MySQL replacement without any changes.
0
Changing Ajenti's webroot (ie my.domain/ajenti)
I'm trying to set up ajenti behind an nginx reverse proxy. The instructions say all URLs are /ajenti, but mine don't seem to be and if I go to myhost:8000/ajenti I get "invalid URL." It's possible that I changed something to get rid of /ajenti but I don't remember what (if anything) I would've done and can't find documentation about that.
0
ajenti cannot connect to mySQL after phpmyadmin installation
For some reason Ajenti connot connect to MySQL anymore after I installed phpmyadmin. What is the reason for this? I give Ajenti the correct credentials but it tells me "access denied". Also a seperate user with all privileges for ajenti won't work.
Answer
Eugene Pankov (Project coordinator)
11 years ago
Can you verify the credentials with 'mysql -u.... -p....' ?
Customer support service by UserEcho
