I'm using xampp for php. but it allows other to look at my pc data which are on same network.
How I can stop this?
Related
I've installed Wireguard on an Ubuntu server, the VPN system works great but I have a problem with a Windows 10 machine in network that has a shared folder. The machine with the shared folder and the personal computer are connected to a VPN but I am unable to access the files as I accessed before. Is there another solution for sharing files on a home network over VPN?
Also I'm unable to use wireless printing, how do I solve this?
More details about the shared folder issue:
I have 2 windows machines one of them holds a shared folder and the other one access the folder and uses the files. I also have an Ubuntu Server that run a Wireguard protocol and serves as a VPN server. Both of the windows machines are connected to the same VPN network through Wireguard.
Prior to the VPN I could access the shared folder through the local network (via hostname) but now I can't find the shared folder in the network.
The way opencpu "productionnise" an app is to get your own linux server then to install your package and then launch your app.
Before that, I am still in a dev environment, where I work on a windows machine.
I would like to run the app locally behind a firewall and send the ipv4 link of my machine to a collegue, to allow him to test my app, using my machine as a server.
Is there a way to serve my app on the Ipv4 address of my windows machine?
From what I understand, on a windows machine, the adviced architecture would be more to use a vm to emulate a linux server. But if there is a way to avoid it, it would be nice.
You can start a local OpenCPU server via opencpu::ocpu_start_server(), which uses port 5656 by default. If you then point your browser to http://<your-ip>:5656/ocpu, you will be greeted with the normal OpenCPU interface.
I have successfully installed Apigility to a remote CentOS server. It tell me to go to http://localhost:8888 to access the admin panel. This server does not have a GUI installed so I don't have the ability to remote in to use a web browser. Is there a workaround to access the Apigility interface remotely, possibly restricting access to my IP address? If not do I have to install it on my local machine and then deploy my work to the remote server?
You could add a .htaccess
file
to set a password on it
If you're deploying to AWS you should be able to configure your SecurityGroup to only allow request to your installation if you're trying to access it.
if you want to develop your application right now I would recommend to have a local installation in a docker container or so to perform your changes. If you're going live you shouldn't change anything in the admin surface either.
centOS server using terminal if i am right. The best way to do this with centOs server in terminal is to open port 8888 to the public and access the server from another system serverIP:8888 (using tools like firewalld in the centOs server. U will have to install firewalld) https://www.rootusers.com/how-to-open-a-port-in-centos-7-with-firewalld/
I am working on a small website based on an example ServiceStack project. It is a standalone web app so that there is no need for IIS etc. Currently I start the server at http://localhost:8080 and opening the website in my local browsers seems to work fine.
My PC has a dedicated IP and I hope to test my server from another computer. I can successfully get a Python server running using python -m SimpleHTTPServer 8000, so network is working fine.
But the remote computer cannot access my ServiceStack server. I think there should be a simple setting somewhere to get it working. But I searched online, there is much information about IIS and ASP.Net. But my app is standalone and is independent of Asp.net. It is supposed to be running on Linux as well as on Windows. (Though I will only deploy on a Windows machine now.)
It will work fine on your local computer because the firewall doesn't block local traffic. If you want any other computer to access services running on your machine you will need to open the ports on the firewall.
This can be configured from the Windows Firewall in Control Panel
I'm running visual studio 2010 on Windows 7 through parallels on my mac. I want to be able to access its local host on osx for testing purposes. I really have no idea what steps that I'd have to take to do this, so any help at all would be appreciated.
Map the VM's IP to a domain in your /private/etc/hosts file in OSX (i.e. testsite.local) or just access via the VM's IP directly. Of course, for the same, map in your VM's host file as well (i.e. c:/Windows/system32/drivers/etc/hosts map 127.0.0.1 to testsite.local)
Map appropriately in IIS in VM.
Make sure applicable port/s are opened in your VM Windows firewall (standard port 80 and 443 usually enough).
Done.
I very rarely use the built-in VS Development Server, so can't say anything on that.
Troubleshooting:
Make sure it works in the VM first ;-)
Turn off your firewall temporarily to make sure it's not a firewall issue.
Make sure you've got your network settings set applicable. I haven't been working with a Mac for all that long, so haven't bothered testing with anything other than bridged.
The answer is NO:
https://serverfault.com/questions/82899/can-i-access-cassini-from-a-remote-machine
Cassini, the built in web server, only listens on Localhost.
The recommended way to do it is to setup IIS 7 on Windows 7 and attach the Visual Studio debugger to your application pool process.
If you can get a tool like Fiddler for Mac that supports reverse proxy abilites you could try:
http://abhishekdev.posterous.com/how-to-access-a-cassini-iis-for-web-projects
Or maybe setup a SSH proxy (VM as the server and ssh tunnely from Mac to VM)?
If you go to Terminal and type in the command "ifconfig" and look for the "vnic1" section which is the last section to be printed and it has an ip address called "inet" e.g. "10.37.129.2" this will take you directly to local host.
If it doesn't work you must ensure that your parallels is set to a shared network under the preferences network section.