I have setup an Nginx reverse proxy on my Raspberry Pi running Fedora Server and nothing will load locally or publicly. Whenever I connect to the ip address of the Raspberry Pi with port 80 I get a message saying the connection was reset. I have looked at other questions here, but none of them have been able to solve my problem. Note: Nginx is running with the default configuration.
Related
I want to connect via TCP socket a server app running in the host with a client running in the QEmu guest.
I use port 5104 for the socket in the server.
I start the server.
Then I found that I can not launch the QEmu giving that port as the input point for the client in the guest, like this:
qemu-system-arm ... -net user,hostfwd=tcp:127.0.0.1:5104-:5104
Gives the error "Could not setup host forwarding rule ..."
I guess that qemu acts like a server also and then the port is already taken by the server previously launched and then is not possible to do it.
Which is the correct syntax? The documentation talks about the option guestfwd but I tried all the possibilities and I couldn't found the solution. It should be way to do it.
Any suggestion?
I have dockerized shinyproxy app and I can reach it through http://localhost:8080. But I cant reach it outside the host computer.
I tried http://my-ip-adress:8080
I allowed port 8080 through windows firewall
I read comments on port forwarding through VM in here. But I am using ubuntu 20. 04 in windows 10 and there is no VM running so I dont know how to do port forwarding.
I tried to run container docker run -itdp 0.0.0.0:8080:8080 shinyproxy-example
But none of them worked.
At the end of the day I wanna get an address put it in an iframe then a website eventually. Am I missing a step or is there another way to do this?
I an new in docker and webdeveloping so any help is appreciated.
I have been tasked to migrate a gateway server "debian 8.1" from a physical server to a VM using CloneZilla.
After running the VM, the VM was working fine and all I have changed is the network card name in:
/etc/network/interfaces
Then network works fine and connect using SSH.
The problem is, services like apache2, svn, bind9 ... etc are working fine "LOCALLY"... but when trying to check these service remotely they are not working.
Example of checking services remotely:
[~]>telnet 192.168.1.1 80 Trying 192.168.1.1...
[~]>telnet 192.168.1.1 443 Trying 192.168.1.1...
[~]>nslookup google.com 192.168.1.1 ;; connection timed out; no servers could be reached
iptables caused the problem by it's rules, I have changed the eth names and it's worked fine.
I configured PPTP on my Raspberry Pi with Wheezy image following the guide given in webpage:
http://www.raspberrypihelp.net/tutorials/21-pptp-vpn-server-raspberry-pi
On completion of the configuration all worked well.
I then installed MYSQL, PHP, APACHE, & PHPMyAdmin, the install went well and all appears ok.
I used this site for guidance.
http://pimylifeup.com/raspberry-pi-mysql-phpmyadmin/
I then tried to reconnect to the PPTP running on the same unit.
Verifying username and password
I now get the error message
'Connecting to 192.168.10.18 using '
The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properl'y
If I do a port scan of the Pi port 1723 does not appear to be open.
Could be the Mysql install has closed the PPTP port?
I have run
sudo netstat -alpn |grep :1723
and the output says
tcp 0 0 0.0.0.0:1723 0.0.0.0:* LISTEN 2567/pptpd
Please can someone advise me of the best way to open the PPTP port?
Thanks
I have got chef-server installed on a centos machine.
Everything is working as expected except that I cannot access the chef-server web interface from another machine on my local network.
I can access the web interface from the centos machine itself:
telnet mychefserver.local 4000
Connected
If I do the same from my machine I have got:
telnet: Unable to connect to remote host: No route to host
I can successfully ping mychefserver.local from my machine
Any idea how to configure nginx with chef-server to access the chef-server from the network?
Since Chef Server 10, the web interface uses normal HTTPS (TCP 443), it only listens on the high ports locally, and nginx proxies as needed to the different backend services. I would try with a normal web browser as telnet isn't exactly great at error messages. Normally I would expect that to mean telnet is getting TCP transmission errors, but maybe it is just confused? If it is really a TCP transmit error then more likely the internal DNS is having issues. .local often means mDNS which has uneven support in some places, I would try an actual IP address to be sure.
My issue was iptables.
I stopped iptables and I can access the chef-server from my local network again.