Installed Scrapyd on rackspace and want to access on local machine - scrapy

I have installed Scrapyd Service on Rack Space. I have dedicated IP. I can access scrapyd on server only [http://localhost:6800]. I want to access this from my local computer and want to deploy spiders later on. I need help to access it like http://someip:6800
Looking forward to hear from you.

Open the port 6800 of your server then you can access it from any machine. You can see how to open port in linux in this link:
http://www.tixati.com/optimize/open-ports-linux.html

Related

Is it possible to host a Minecraft server on GitHub Codespaces?

I downloaded the Fabric server jar file to a GitHub Codespace and am able to run the server without trouble. However, I am unable to determine the IP needed to connect to the server. Starting the server automatically forwards port 25565 and I make the port public. However, I can't figure out which IP to paste into Minecraft to connect to it. How do I figure out the IP of the server?
I found an answer thanks to inspiration from this question.
Steps:
Set up the fabric server jar as you normally would, but on the codespace. Start the server.
Split the terminal so one is running Java (server console) and the other is running bash.
Install ngrok via npm i ngrok --save-dev.
Once the server is finished setting up, run the command ./node_modules/.bin/ngrok tcp 25565.
Copy the ip shown under Forwarding (minus the tcp:// part and including the port). This should look something like 4.tcp.ngrok.io:17063.
You now have the ip of the serve!
Note: The free version of ngrok has URLs which change every time, as well as a limit, but for small-scale servers this shouldn't be an issue. You are also limited by the free codespace usage limit GitHub puts in place. However, you can easily get around this by creating a secondary account that you use codespaces on only for the server.

Web access to Gluu v4.0 server, installed on Ubuntu 20 machine

I have installed Gluu server version 4.0 on an Ubuntu ver.20 powered machine. After running setup script I am able to login to server from command line and according to Gluu docs I should be able to access UI from web browser using this pattern https://<hostname-where-gluu-server-installed>.
But this doesn't work. I have enabled port 443. Both browser and server are on the same machine. Thanks in advance for your answers!
Gluu must be deployed on a server or VM with a static IP Address. The static IP address should resolve to a computer hostname which can be achieved by adding an entry to the DNS server or in /etc/hosts.
More information on official Gluu docs:
https://gluu.org/docs/gluu-server/4.0/installation-guide/

Is it possible to host a website on a computer but use the static IP from a vpn-server on a google cloud vm?

I have my website up and running on a google cloud vm. But it runs slow because i only use the cheapest one. Before upgrading the vm to a more powerful one, is it possible to host a website on my own computer using the IP from google cloud vm? I successfully set up a vpn server on it using softether (checking whatsmyip on my computer shows the public IP from google cloud vm). Any tips and help would be appreciated.
VPN is usually for outgoing connections, not incoming. Generally speaking, you would need to have some kind of thin server running on your cloud instance, that forwards all incoming connections to your home machine. From visitors' perspective they will be connecting to the cloud IP, but all the work will be done by your home PC.
Of course your home PC will probably have a dynamic IP so it will have to keep the server updated on this.
Here is one very simple implementation. Do not actually do this, it is just an illustration:
Run your website on your home PC so that it serves on eg. localhost:8000
Set up an SSH server on your home PC
SSH into cloud PC
From there, SSH back into your home PC with SSH forwarding of localhost:8000
Run the reverse proxy (eg. nginx) on your cloud PC and tell it to proxy to localhost:8000
Requests will be proxied to your home PC through SSH so long as the connection is alive. This is obviously not a convenient setup and letting a cloud machine SSH into your home PC is a bad idea for many reasons. You could try to restrict the SSH into your home PC, or even run a VPN server at home and have your cloud instance connect to that VPN to access the website. However that is still not a best practices way to do it.
A better way would be:
Obtain a stable URL (doesn't have to be a full domain, just something that can forward to you IP)
Run an nginx reverse proxy on your cloud server, and tell it to proxy to this URL
Ensure the URL points to your home PC when you IP changes (ideally you want an "update IP" script that runs everytime you turn on your home PC)
If you don't want a URL, you could also write a simple script to update a hosts entry on the remote machine with your home PC's IP.

Access the glassfish server web application remotely

I am able to access an application on glassfish server locally via http://localhost:8080/domain1 or http://<machine-ip>:8080/domain1. However, I am unable to access it from another remote machine.
When I put http://<machine-ip>:8080/domain1 in a browser, connection timed out.
Firewall is off on both machines and I have also add machine-ip to /etc/hosts file. I can ping glassfish server machine I am using redhat enterprise 6.3 linux on which glassfish is installed.
Please tell how to access it via IP. DO we need to change any configuration file?
Any help would be really appreciated.
Thanks
-Sam
This might be a problem because of Selinux policy being in enforcing mode.
Try changing it to passive or disabled mode and then try accessing your server.

Can't access ec2 webserver

We are using an ec2 instance with windows 2012 just installed Apache 2.4 with an elastic IP.
I can log on using Remote desktop just fine. We can access the webserver locally using localhost but we cannot access it from outside. We have even tried opening up all ports and all IPs to make sure we didn't do anything wrong.
WE have worked with Linux servers like Ubuntu in the past on EC2 instances. Even though we are familiar with AWS Firewall and Security Groups we did miss that Windows has its own Firewall. Changing the Windows Firewall rules was the solution.