currently i can not access and services of my VM, browser SSH connections, 443 and 80 ports are not answering any requests. First i thought, somehow my TCP ports closed but then when i check them i realised they are active. Is there any person had same issue as like mine at past ?
I could'nt gave more techinal informations currently cuz of my less knowledge about managing VM's. If you ask me some results or response of tricks ill be there for get results and share on here.
Regarts from Turkey, thanks for all kind entrys.
Related
at my firm we have a jupyterhub/lab installed and is used by roughly 70-100 people in a secure network that can only be accessed to from work. Recently the idea of hosting web-applications for short time use came up, but we are having port problems. User A is running a web application on port 5000, and User B can’t use the port because it is already in use. Port 5000 is default, it can be changed but this is not the behavior we want. Does anyone know of a way for web-applications to run on the same port in the same environment? Have looked into server-proxy but i do not really understand it. Is the way to achieve this really to be running a vm for each user securing that the port is not in use?
Any help is appreciated
I'm trying to setup a Squid server on a virtual machine, and there will be another machine which will be connecting to the internet via Squid server. The problem is I couldn't find out how to get traffic with Squid server. I've read that port-forwarding is the way to go, and searched for it. Still, no examples/answers about that matter. I've wrote the rules for Squid, and tested it. It's not catching the traffic, at any level. Anything will help me out of this.
Thanks in advance.
I wrote a post about this a number of years ago to do something very similar - you can read about it here: http://ashleyangell.com/2009/03/configuring-a-basic-reverse-proxy-in-squid-on-windows-website-accelerator/
I have been asked to take over a project where the previous developer had used socketio4net,
hence I learnt of the socketio4 project only now.
the problem my employer is facing is clients having proxy servers.
we have installed our product(client side) on clinics which uses socketio4net and websocket.
They all connect to our main azure server for sending data. In clinics without proxy,we are not facing any issues. but those with proxy server, our service is not even starting.
if we have to implement the ssl process, it will be a big overhead for us
how do we achieve ssl and proxy settings for sockets in general? does socketio4net provide any other options?
do I have change to http classes like webclient?
In my experience with proxies and school's in particular, the vast majority turned out to be a firewall based issue.
What port are you using, 80, 443 or something else? If that is the issue, the clinics would need to either whitelist your server ip, or allow the ip:port combo you've set.
For a quick test at the clinics that have issues - I would try these two sites (probably others sites you can find too):
http://websocketstest.com/ - tests for ports 80, 8080, 443 with and without ssl - do all or only some work?
(this site is also great for a end-user at the site to run for you, as you can get a results link - double bonus points!)
http://www.websocket.org/echo.html
Are both of the sites above able to connect?
Hope that helps...
I am trying to setup a pptp server on Centos,
I open port 1723 (pptp port) with no issues when setting up pptp, and I do a nmap scan to confirm that it is open, however when I nmap the server remotely, it doesnt even list port 1723, by which I assume that port 1723 is not accesable
Is there something I am missing, forgetting
p.s., my first time setting up, so I am noob, please forgive any mistakes or missunderstandings and please dont down vote, I really need help and posting on serverfault apparently is of topic for this too...
UPDATE after #Calvin
Thank you for your informative response, do you know of anyway I can check where it is being blocked???
It is probably being blocked by a proxy server/firewall that the remote request has to go through. So for example, you're in one location A, wanting to connect to the other location B (which you've said is setup correctly and open to requests), though the security apparatus at location A have blocked outgoing requests to whatever port range, and likely outside your control unless you know the network administrators to check with them.
Is my first assumption.
forgive the triviality of my question. I was asked this question and I wasn't able to find a proper answer so I decided to research this myself and understand. I have spring ,maven etc background. Supposing I deployed my web app on a box 192.168.0.10 in my network, can I listen on the port say 9090 of the 192.168.0.10 and do something with it in my application itself running on tomcat7 on the usual port 8080.
What all this is supposed to do is listen on a port and display a graph on the client side based on the value received.
I was thinking using maven, I will have a jar packaged project handling the networking bit and transfer the control to the web app.Event that it's really blur in my mind.
Can anyone clarify things a little bit for me?
Thanks in advance
Why do you need a different port, effectively your web app is already callable on the port provided by tomcat. You can have various servlets each distinguished by URL, and one can return graphs. There's lots more possibilities, but I don't see any need for another port.