I've installed otrs 6 on a system with Centos 7 and with name test.domain.local. Now I've changed the name into ticket.domain.com. I've changed /etc/hosts and /etc/hostname and then I reboot the server. Now when I try to access to the site http://ticket.domain.com/otrs/index.pl it shows:
Message: Access denied for user 'otrs'#'ticket.domain.com' (using password: YES)
I have already changed in the /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm.
Can anyone help me ??
Related
I have a digital ocean droplet in that I have installed Centos 7.5, and on that, I have installed CWP, with that there is some problem. the problem is that I have created the emails in that CWP when I try to login the Roundcube using that email then it redirects me to the blank page. and when I debug the round cube then I got one error in the network that when I enter the email id and password and click on the login then I saw the 500 internal server error in the post request of Roundcube.
I have also tried by deleting the emails from CWP and also checked by creating new emails but the errors remain, and also I have deleted the droplet and created the new droplet and tried doing so but the error still exists.
I have installed CWP el7-latest.
Error Logs
[11-Feb-2019 07:13:36 UTC] PHP Fatal error: Uncaught Error: Class 'Net_IDNA2' not found in /usr/local/cwpsrv/var/services/roundcube/program/lib/Roundcube/bootstrap.php:405
Stack trace:
#0 /usr/local/cwpsrv/var/services/roundcube/program/lib/Roundcube/rcube_utils.php(891): idn_to_ascii('localhost')
#1 /usr/local/cwpsrv/var/services/roundcube/program/lib/Roundcube/rcube_utils.php(869): rcube_utils::idn_convert('localhost', true)
#2 /usr/local/cwpsrv/var/services/roundcube/program/include/rcmail.php(600): rcube_utils::idn_to_ascii('localhost')
#3 /usr/local/cwpsrv/var/services/roundcube/index.php(109): rcmail->login('support#buywpte...', '', 'localhost', true)
#4 {main}
thrown in /usr/local/cwpsrv/var/services/roundcube/program/lib/Roundcube/bootstrap.php on line 405
If anyone knows please help.
Anyone looking for the fix in 2021 here is what I used http://forum.centos-webpanel.com/index.php?topic=11376.0.
curl -s -L https://www.mysterydata.com/upload/tmp/cwp_rc_fix.sh | bash
Run this SSH Command to update roundcube on your CWP
sh /scripts/mail_roundcube_update
I have a VmWare VPS and Using CWP7 on CentOS 7.5 and I am using apache server only . I have successfully installed Lets Encrypt SSL for my server FQDN (host.domain.com) .
When I am using certbot for new SSL for another domain (realmart.net), it's showing error and unable to verify the location http://realmart.net/.well-known/acme-challenge/ .
When I am accessing the URL , it;s showing the error below :
"You don't have permission to access /.well-known/acme-challenge/ on this server."
I have set the write permission for that location But another directory is accessible: http://realmart.net/.well-known/
Then I try with https://www.sslforfree.com/ for that certificate and I have created /.well-known/acme-challenge/ manually with the right permission then it's showing the same error.
Is there any way to verify or browse the location http://realmart.net/.well-known/acme-challenge/ ?
Please suggests ...
Story: Few days ago CWP admin Team has been removed LetsEncrypt module and added AutoSSL . I think CWP Team block that's type of verification that user will be used to AUTO SSL.
Try uploading your verification files in
/usr/local/apache/autossl_tmp/.well-known/acme-challenge/
we have 3 node and trying to setup hdfs and pivotal hawq with ambari and i have already enabled passwordless ssh for all the 3 machines but when i start hawq service i am getting "Setting up passwordless ssh failed for all the HAWQ hosts" this error please help to resolve this issue.
enter image description here
On all of your hosts, edit your /etc/ssh/sshd_config file and change "PasswordAuthentication no" to "PasswordAuthentication yes". This can be done with sed too.
sudo sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config
Then restart sshd on all of the hosts:
sudo /etc/init.d/sshd restart
Now you can proceed with the installation of HAWQ. The installation is using a command called gpssh-exkeys. This process uses password authentication to communicate with the hosts so that it can create and exchange keys for the gpadmin account. Once the keys have been exchanged, the gpadmin account no longer needs password authentication.
Also, after the installation is complete, you can revert back and disable password authentication if you like.
Lastly, I've asked the PM for HDB at Pivotal to enhance Ambari to do these steps for you automatically. There is a similar process for iptables being disabled during the installation of Hadoop so this would be like that. Ambari would enable password authentication, install HDB, and then disable password authentication.
I have a Django web server on a VirtualBox/Vagrant machine running Ubuntu.
I have followed this guide to create a Django project: https://docs.djangoproject.com/en/dev/intro/tutorial01/
I have a web server running at http://127.0.0.1:8000/ inside my guest machine. This is the first time I am running a Django web server. It is supposed to be a hello world app.
How can I access this web application from my host browser?
I have tried running ifconfig in the guest to get the IP that I should visit I found a promising IP address in inet addr.
But I have tried entering the following into my host browser and it didn't work.
http://inetaddrnumbers:8000/
How can I access the web server from my browser?
Try this.
Open the vagrant file (should be in the directory where you specified to create a new vagrant machine).
Search for config.vm.network. If you didn't setup the file earlier, it should be commented.
Change it to look something like this config.vm.network "private_network", ip: "55.55.55.5". Here ip address (55.55.55.5) can be any ip address you want.
Now logout from the vagrant machine and reload your vagrant machine by this command vagrant reload.
Again ssh to your vagrant machine and restart your django server by this command python manage.py runserver 0.0.0.0:80. Again the port address (80) can be 8000 if you want so.
After that, in your browser, enter the following address 55.55.55.5, and hopefully you should see your webapp.
Now if you would like to go further, you can edit your host file, and add this line
55.55.55.5 mynewdomain.com
Then in your browser, enter the follow address,
mynewdomain.com
And you should see your web app. Note that, www is not added in the domain name inside the host file, so only mynewdomain.com can be accessed. You can however add it.
Hope this helps. Cheers.
Complementing #Kakar answer, this configuration can also be done using this:
config.vm.network "private_network", type: "dhcp"
This will assign an IP automatically.
For further reading: https://www.vagrantup.com/docs/networking/private_network.html
The command vagrant up is failing and I don't know why.
$ egrep -v '^ *(#|$)' Vagrantfile
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise32"
end
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
The VM failed to remain in the "running" state while attempting to boot.
This is normally caused by a misconfiguration or host system incompatibilities.
Please open the VirtualBox GUI and attempt to boot the virtual machine
manually to get a more informative error message.
$ vagrant status
Current machine states:
default poweroff (virtualbox)
The VM is powered off. To restart the VM, simply run `vagrant up`
$ VBoxManage list runningvms
$
Here are the messages in the VirtualBox log file, VBoxSVC.log:
$ cat ~/.VirtualBox/VBoxSVC.log
VirtualBox XPCOM Server 4.2.16 r86992 linux.amd64 (Jul 4 2013 16:29:59) release log
00:00:00.000499 main Log opened 2013-08-13T18:40:45.907580000Z
00:00:00.000508 main OS Product: Linux
00:00:00.000509 main OS Release: 3.6.11-4.fc16.x86_64
00:00:00.000510 main OS Version: #1 SMP Tue Jan 8 20:57:42 UTC 2013
00:00:00.000537 main DMI Product Name: X8DA3
00:00:00.000547 main DMI Product Version: 1234567890
00:00:00.000647 main Host RAM: 24103MB total, 17127MB available
00:00:00.000654 main Executable: /usr/local/VirtualBox/VBoxSVC
00:00:00.000655 main Process ID: 9417
00:00:00.000656 main Package type: LINUX_64BITS_GENERIC
00:00:00.110125 nspr-2 Loading settings file "/opt/tomcat/.VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.110817 nspr-2 Failed to retrive disk info: getDiskName(/dev/md126p1) --> md126p1
00:00:00.264367 nspr-2 VDInit finished
00:00:00.275173 nspr-2 Loading settings file "/opt/tomcat/VirtualBox VMs/vagrant_getting_started_default_1376419129/vagrant_getting_started_default_1376419129.vbox" with version "1.12-linux"
00:00:05.288923 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium '/opt/tomcat/VirtualBox VMs/vagrant_getting_started_default_1376419129/box-disk1.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:05.290229 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
$
Any advice would be greatly appreciated.
Had the same error on OSX. Restarting VirtualBox fixed it :S
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
Also see: https://forums.virtualbox.org/viewtopic.php?t=5489
I solved the problem by re-installing VirtualBox and adding myself to the vboxusers group. The re-installation process printed a message indicating that VM users had to be a member of that group. I don't know if the re-installation was necessary or if being added to the group would have sufficed.
The host machine was 32bits (Ubuntu) and the guest was 64bit, I changed the guest to 32 and it solved the problem.
My understanding is that vboxusers group is related to accessing USB devices within the guest. Not sure why it is causing the issue. Normally, as a vagrant base box build guideline, audio and USB are both disabled.
As per the VirtualBox Manual => The vboxusers group
The Linux installers create the system user group vboxusers during installation. Any system user who is going to use USB devices from VirtualBox guests must be a member of that group. A user can be made a member of the group vboxusers through the GUI user/group management or at the command line with sudo usermod -a -G vboxusers username
Note that adding an active user to that group will require that user to log out and back in again. This should be done manually after successful installation of the package.
I had the same problem. It is because I did a wrong configuration on my Vagrantfile in the provider section. I had tried to make my VM machine more powerfull, with 2 cpus when i have on the machine host just one.
this often happens when you try to add more hardware to your VM machine but your host machine does not have the minimun requirements