This server worked not too long ago (I don't have a specific date). We use it for testing and had successfully deployed a few applications. Upon returning to the project I could no longer access the applications chrome saying the site cannot be reached when I netstat -an | grep 'LISTEN'.
I can see the unsecured port but the SSL port is missing in action. I asked the networking team if the ports were being blocked and they said no. I tried to force the application to use the secure port by disabling the unsecured port, restarting the managed server but the it fails to start with this configuration.
Any thoughts? SSL is not really my area of expertise (this is my first exposure). When googling the title I didn't see any results that matched the problem I am having, or at least I did not realize they did...
The server will restart if I enable the unsecured port.
# Gerardo Arroyo, yes this seems to be the issue. I assumed that this server used the same certs as other servers in the test system but it seems I was wrong. I will request a new cert from the networking team. Thank you
Related
I am running into an issue trying to enable hyper-v replication on Windows Server 2016. I have tried via HTTP and HTTPS (AD signed certificates) and neither works. The interesting thing is, I already have another VM replicating between the two servers so I know its possible.
The current error is:
[Main Instruction]
Enabling replication failed.
[Expanded Information]
Hyper-V failed to enable replication for virtual machine 'VM2': The operation timed out (0x00002EE2). (Virtual machine ID 134E9F3F-XXXX-XXXX-XXXX-1AC608804212)
However this doesn't make sense as I can ping the server (ping works from both sides) and I can connect to port 80 and 443 from each side (VS1 and VS2) - note they are on different subnets however that shouldn't matter. Also both servers are part of the domain so authentication shouldn't be an issue (I am logged in as a domain admin and have a valid kerberos ticket) and there is nothing in any of the event logs that gives me any sort of clue as to what is wrong.
Anyone have any ideas of what might be wrong?
just had the same problem. This link helped me a lot:
https://social.technet.microsoft.com/wiki/contents/articles/24258.hyper-v-troubleshooting-error-0x00002ee2-while-enabling-replication.aspx
as described it could be a problem with your routing. I was able to solve it by enabling BypassProxyServer
the powershell command should look something like this (Keep in mind that this configuration is powershell only):
Set-VMReplication -vmname "name" -AuthenticationType Kerberos -ReplicaServerName "servername" -ReplicaServerPort "Port" -BypassProxyServer $true
I've been searching and haven't found a solution for this yet.
I have a LAMP server running Centos 5 and cPanel. I have converted the site from http to https. The site works just fine. However, periodically there are ERR_CONNECTION_REFUSED errors on my PC only. This happens only over https and only periodically. Port 443 is open on the server.
FTP, Remote MySQL, SSH, and HTTPS connections are refused during that brief period. I've checked the server's firewall to allow my ip and unblock my ip. The ip is allowed and was never blocked.
We have other PCs connected to the same network with no issues during the brief period where only my connection is refused. I've cleared my cookies and cache with no luck. However, when I run a trace route, it stops at the first hop in our network.
Any suggestions with what I need to do or look at?
Do you think it is a server related issue?
Do you think it is an internal network related issue?
Could it be the issuer of the SSL cert?
You're probably running into a full backlog queue. A Windows server will actively refuse a connection if the backlog queue is currently full. The defence is to increase the backlog or speed up the accept loop.
We have been battling with an issue where I've been getting a 5006 error using "SagePay Server" for 24 hours after moving a nopcommerce site to a new server with a different IP address.
We use a free cloudflare service with SSL enabled on Cloudflare in Full SSL mode and then a self signed certificate on our server so the connection is always secured end to end. This was also the same on the old server.
When moving servers we simply updated the IP address in couldflare to point at the new IP address but we started getting 5006 errors during the checkout process...
SagePay support told us they could not connect to our notification URL which was using SSL. Our server showed no attempt from their server to connect to ours yet SapePays log files show an "internal_error" with no more useful information.
However it is possible to the call the notification URL passed to SagePay from a browser and it works without issue.
After talking with SagePay on several occasions it would seem the SagePay system does not support websites / traffic using SSL with SNI which means they can not connect to the notification URL over SSL.
In a time when IPv4 addresses are fast running out I would imagine more and more people will start to use SNI for SSL so they can run multiple sites using SSL from one IPv4 address - a massive oversight on SagePay's part me thinks.
Contrary to JaxUK, I can confirm SagePay does support SSL/TLS with SNI. Hope this helps someone
I've got an abuse message from Spamhouse with following:
The host at this IP address is currently being used to distribute malware.
Malware distribution located here:
http://xxx.xx.xx.xxx:8080/get/get.php
Where http://xxx.xx.xx.xxx is our domain.
We've found that any request to port 8080 returns Malware.
We use Apache 2 on server. But there are now any setting on port 8080.
Just looing for ideas how to fix that bug?
At the moment we closed port 8080. But there are still some malware inside.
Will appreciate for any suggestions.
Pull that server offline now.
Deploy new server.
Ensure all relevant OS and application updates are applied.
Double check security configuration.
Restore your data from a verified backup.
Then investigate the original server logs/etc. for clues as to how you were infected in the first place.
I used nmap to check which ports are open on my server it showed
PORT STATE SERVICE
9090/tcp open zeus-admin
now port 9090 is supposed to listen for apache tomcat. What is this zeus-admin ?
how I start my apache tomcat server ?
It is also the default listed name when nmap'ing it. The actual service listening to that port doesn't have to be, it's what is usually the default service running at that port.
Zeus Web Server is a proprietary web server for Unix and Unix-like platforms.
ZWS seems to be dead since it hasn't been updated since January 2010, and the company no longer offers a similar server solution.
It's probably fine to just kill it, and remove it from operation as it's mostly just a security risk by now.
Zeus is sometimes used as an embedded web server for things like admin consoles. If you have the OpenFire XMPP server installed, you will find the configuration UI tools running on port 9090 (http://localhost:9090).