I have installed Roundcube on local machine and it works fine, but with same configuration, it is not working on server. It's giving an "Connection to IMAP Server failed" error.
$rcmail_config['default_host'] = 'ssl://imap.gmail.com:993';
Log:
> [17-Jan-2011 03:05:06 +0400]: IMAP
> Error: Login failed for
> xxxxx#gmail.com from xxx.xxx.xx.xx.
> Could not connect to
> imap.gmail.com:143: Connection timed
> out in
> /home/xxxxx/public_html/rc/program/include/rcube_imap.php
> on line 183 (POST
> /mail/?_task=login&_action=login)
I'm wondering - why is it trying on port 143, when port #993 is written in config.
You have to set the configurations as follows
$rcmail_config['default_host'] = 'ssl://imap.gmail.com';
$rcmail_config['default_port'] = '993';
it should work , if not check with the below commands whether it is possible to connect to the sever through commands as shown below:
ping imap.gmail.com
telnet imap.gmail.com 993 [for Windows] or telnet imap.gmail.com:993 [for UNIX]
If you are able to get the successful output. you will be able to connect to the IMAP Gmail server via Roundcube.
Port 993 is default for ssl://. the problem is with your server as sometime due to limited memmory by hosting provider they can't connect to gmail. I had a similar situation. I could connect to other mail server from my hosting server but not gmail. Then i switched hosting to other company and same code worked.
Related
I'm having a hell of a hard time trying to figure out why I can connect to my SQL Server using Management Studio using my local ip or local computer name or sql instance name but I can't connect to the same SQL Server using my public ip address.
I have tried all of the below steps but nothing seems to fix the Wait Operation Timed Out error message:
Disabled firewall on the SQL Server and the computer I'm trying to use to connect with.
Port forwarding is enabled for the port I'm using which is the default 1433
Ran the telnet command: telnet publicip port from a computer outside of my network and it was successful
Restarted the SQL Server plenty of times
Enabled remote connections for the server and enabled tcp/ip for the 1433 port
I also enabled port forwarding for the sql browser service using the recommended port of 1434 via udp
Tried to connect with named instance but only works with local ip and not public ip
I am pretty much out of ideas at this point so any help is greatly appreciated
Here is the full error message just in case anyone needs to see it:
Cannot connect to XX.XX.XXX.XXX,1433.
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.) (Microsoft SQL Server, Error: 258)
I have a very simple LAN setup and am trying to connect to an Apache server running on the LAN. The server IP is 192.168.1.178. I'm trying to connect from a box on same LAN with IP of 192.168.1.161. Attempting to connect from browser results in error saying site is unreachable. I can ping the server and SSH into the server. But, telnet and curl result in no route to host errors.
Both boxes are set up with static IPs. DNS for static connection is 192.168.1.1. Both boxes are running Manjaro and no firewalls are turned on. Apache access logs show no attempt to connect and there are no errors in the Apache error logs.
I also set up a test python server (sudo python -m http.server 80) to try that. Attempting to curl to that server results in 'connection refused' error as opposed to 'no route to host' error for the Apache server.
Traceroute results are:
traceroute 192.168.1.178
traceroute to 192.168.1.178 (192.168.1.178), 30 hops max, 60 byte packets
1 raptor (192.168.1.178) 0.434 ms !X 0.366 ms !X 0.400 ms !X
I discovered that a firewall daemon was running, which was causing the problem. Disabling the firewall solved the issue.
I am trying to connect to RabbitMQ with EasyNetQ.
RabbitMQ is on remote VM.
_rabbitBus = RabbitHutch.CreateBus(
string.Format("host={0};virtualhost={1}",
_hostSettings.Host, _hostSettings.VHost),
x => x.Register<IEasyNetQLogger>(l => _logger));
_rabbitBus.Subscribe<Message>(_topic, ReceiveMessage, m => m.WithTopic(_topic));
I get a TimeoutException The operation requested on PersistentChannel timed out..
Remote VM is replying to pings, ports 5672 and 15672 are opened (checked with nmap).
RabbitMQ management can be accessed from my host.
Also, if RabbitMQ is run on my local machine, it works fine.
I've tried connecting to RabbitMQ installed on my computer from other pc's in LAN, and it also works.
I've come to an assumption, that it's related to the fact it's on a virtual machine, and maybe there's something wrong in connection. But again, Rabbit's web management works fine.
Also tested on EasyNetQ Test application - works on localhost, but not on remote.
Output as following:
DEBUG: Trying to connect
ERROR: Failed to connect to Broker: '192.168.0.13', Port: 5672 VHost: '/'.
ExceptionMessage: 'None of the specified endpoints were reachable'
ERROR: Failed to connected to any Broker. Retrying in 5000 ms
EasyNetQ v0.28.4.242
As Mike suggested i had this and then checked the permissions. "guest" user can only connect via localhost (see RabbitMQ Access Control.) Try adding a user with permissions using the management interface and then connect as below
var _bus = RabbitHutch.CreateBus(string.Format("host={0};virtualhost={1};username={2};password={3}",
_hostSettings.Host, _hostSettings.VHost, _hostSettings.UserName, _hostSettings.Password));
Did you check your credentials. The default username and password is 'guest' and 'guest'. The error message is not very helpful. You get 'None of the specified endpoints were reachable' if there's an authentication error as well
I want to create localhost connection in Oracle SQL Developer tool
my credentials are
username : SYSTEM
password : SYSTEM
Hostname :localhost or 127.0.0.1
port : 1521
sid : xe
When i connect i gives error The Network Adapter could not establish connection
The Network Adapter could not establish connection is caused because:
The database host name or port number is wrong.
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
you have either the wrong SQL Developer URL or you have a basic SQL*Net connectivity issue! This error is most likely caused by one of these factors:
You are using the wrong URL
The wrong port number or IP address (or DNS host name) was used
The listener is not configured properly
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
For a step by step checklist, see the notes on troubleshooting an Oracle connection problem.
Does anyone know why I am unable to connect to my server using the Notepad++ NppFTP plugin with SFTP?
I have a CentOS 6.4 server with SSH on port 22.
When I try and connect using NppFTP I get the following output:
[NppFTP] Everything initialized
Connecting
[SFTP] Connection failed : Error reading socket
Unable to connect
Disconnected
This used to work when I had my SSH port set to 3264 but when I changed the SSH port back to 22 NppFTP stopped working. All the settings for the profile are correct including the right IP, username, password and port (22).
I can connect with SFTP using FileZilla and WinSCP successfully with these same SFTP details and I can connect with SSH using PuTTY.
I can connect with SFTP to other servers using NppFTP so I believe there is an issue in my server config I'm just not sure where or what.
I looked at the access logs but found no attempt at a connection from NppFTP, I turned the firewall off and still nothing.
In the end I got in touch with my server company and it turns out it was a problem on their end. This is what they had to say:
"This was caused by an IPS rule inspecting the network packets coming into the infrastructure, which helps identify brute force attacks."
Very strange, but after they made the change NppFTP can now connect successfully.