Can't Connect to Apache Server on LAN - apache

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.

Related

Gitlab change ssh port (ubuntu 22.04 LTS, gitlab-ce 15.8.1)

I'm running my own gitlab server on Oracle Cloud
and its Domain handled by Cloudflare
But my gitlab ssh cloning doesn't work at all.
(as far as I can remember, HTTP 413 curl 22 The requested URL returned error: 413)
(And It also happened port 22 network unreachable error)
I think other process hold 22 port, so I tried to change gitlab ssh port to other port.
Changed gitlab.rb (gitlab_shell_ssh_port to other)
Open Oracle Cloud VCN port,
Open Ubuntu Firewall(ufw allow and also tried iptables)
And Add other port on sshd (/etc/ssh/ssh_config)
disable cloudflare DNS Proxy to DNS only.
but It doesn't work and even port is inaccessible.
more than that nothing listen on that port.
what should I do more on this?

Cannot connect to Apache on Google Compute Engine

I have set up a Google Compute Engine and installed Apache on the server.
(The server is running Windows 2008 Server and Apache is running as a service.)
I can connect the server using Remote Desktop. However, I am not able to connect to the webserver. (I have also installed a FileZilla FTP server, but annot connect to ftp either.)
I have opened access to ports 80 and 443 on the Windows firewall, and I have also opened access to the same ports on the VPC Network Firewall:
default-allow-http
Ingress
http-server
IP ranges: 0.0.0.0/0
tcp:80
Allow
1000
default-allow-https
Ingress
https-server
IP ranges: 0.0.0.0/0
tcp:443
Allow
1000
Still, I am not able to connect to the webserver. I cannot connect to the webserver when I am logged on using Remote Desktop and then trying to connect to 127.0.0.1, either.
I have a similar setup on a virtual server on Rackspace. There everything works as expected. Any tips on what I might be doing wrong?

Start a WS connection on a server that's being accessed by SSH port forwarding

I have an EC2 Instance(A) and a RaspberryPi(B). I want to access a HTML page in B.
Here are the steps I did:
Created a simple index.html in B that connects to a WebSocket running on 5443 also in B
Served it with SimpleHTTPServer on port 1337
Created a port forwarding. When I access A:9000 it should redirect to B:1337. Used: ssh -f -N -R 9000:127.0.0.1:1337 A
With that I'm able to access my index.html page, however it fails when trying to connect to the WebSocket server with
WebSocket connection to 'ws://localhost:5553/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
When I use VNC to connect to B, and access the browser in localhost:1337 I'm able to see the page AND the WebSocket connection succeeds.
I'm not sure why it fails when I try to access it through the EC2 instance. Does anyone have any clues on what might be the problem? thanks
**All ports are open in my EC2 instance
Even though I was port forwarding, localhost:5553 wasn't the raspberry pi IP, was the EC2. I created a new port forwarding from 9001 in A to 5443 in B to tunnel the Websocket connection and it worked.

Enable Remote SSL on Weblogic

I've enabled SSL Listen Port from the Admin Console of Weblogic 11g Version: 10.3.6.0
I've created a self-signed cert following: https://oracle-base.com/articles/11g/weblogic-configure-ssl-for-a-managed-server
But when try https on the browser of a remote machine I get a timeout.
If I try from the local machine using: curl -Ik I get the proper response, it seems that only remote access is disabled.
Accessing via http works fine from my remote machine browser. I did also try telnet but it only works with 7001 but not with 7002 (my secure port). I've already tried changing the secure port number but the result is the same.
My Weblogic server is on a Centos running on VMware ESXi.
What could be blocking the remote SSL connection?
A timeout indicates a firewalling of some sort. As you say yourself if you try locally with curl it works. There is nothing else to check if locally you can but remotely you get a timeout.

IBM Server configuration

i have an ibm server, a tp-link router with an static ip and DHCP activated, i want to configure one of the net boards in the ibm server.
I installed Ububntu server and access to the net board configuration using this command:
vi /etc/network/interfaces
I configure the server with this
address -> i put an ip that i resrve in the router
netmask
network
broadcast
gateway
I have a subdomain from no ip i have entered in the server so i can do remote connection to the server throw this subdomain and ssh. I have put the subdomain in /etc/host.conf
The thing is i have access to the subdomain in the web and out of the LAN net. But when i try to connect to the server throw ssh it's gave me connection refused.
EDIT:
Using the command arp-scan -I eth0 -l i found that the IP of the server is asigned two times it's look like it's the same ethernet board with two MAC address thar are the same except the las number.
Ok, what's work for me was to reinstall openssh on the server and in my computer. After that I have access throw ssh.