Is it possible with current version of VisualStudio and XCode 11.5 can we access the MacBuild machine over the internet?
I have configured Mac machine with remote login enabled, setup noip, setup SSH port forwarding 22 on router and below are the results.
Initially, Pair to Mac has got the fingerprint but after providing the username and password it failed to authenticate as in picture 2.
any ideas ? or some one already using Pair to Mac over the internet.
Related
I'm working with Visual Studio 2015 on a Windows computer and I want to simulate my app on a MacBook via remotebuild. But the VS Remote Agent Client is not able to connect:
If I try to establish a connection with security PIN, it says:
"An error occurred trying to acquire certificate from https// ..."
If I try to establish a connection without security PIN, it says:
"Unable to connect to remote iOS build server. Underlying exception: The remote server returned an error: (403) Forbidden."
If I run Apache Cordova on the Mac, there aren't any problems. And also my Xamarin App works on the remote iOS simulator. So why is it not possible to run my Apache Cordova App there, too?
Maybe it is relevant to mention, that I do not have an Apple Developer Program Account.
Make sure, you MacBook and VS workstation both are in same network. Also verify using command prompt that MacBook's IP add
Replace host name using IP address MacBook and try again.
If this does not work then following are steps to reset remotebuild:
first stop server using following command:
cntrl + c
Execute following command to reset remotebuild certificates:
remotebuild certificates reset
Run following to command to regenerate remotebuild server:
remotebuild certificates generate
here, new secure pin number will be generated.
Following command to start remotebuild:
remotebuild
now try again, make sure 'Enable remote iOS processing' is true and 'Secure mode' is true and valid secure number is added.
I will simulate my app using the Apache Ripple simulator for iOS and Android, although "Ripple doesn’t provide a complete simulation of Cordova APIs or native device capabilities (plugins). It also doesn’t simulate specific browser versions for a particular platform." (https://taco.visualstudio.com/en-us/docs/run-app-ripple-simulator/)
But it's better than nothing...
Trying to test a local web app developed on my mac running El Capitan using my iPhone. I'm able to pull up the web app using my internal ip on the actual mac, but when using another device connect to the same network it's not working. This use to work fine on previous versions of osx, but ever since upgrading to El Capitan, this hasn't been working properly.
Any hints or solutions to this problem?
Thanks
I have a website on my Mac running off MAMP. I couldn't connect to it via IP on another computer. I turned off the firewall on the Mac and could connect by just typing in the IP into the address bar. Mine happened to be 192.168.1.69. To get the actual website, I did have to include the port number, i.e 192.168.1.69:8888. Make sure that you are using your private IP, not your public one (should start 192.168.X.X or 10.X.X.X). This worked to connect from another computer and from my phone.
I have a small LAN with:
A Synology server where I have installed a Comodo Wildcard
Certificate for mydomain.com.
Three wired clients running Windows 8.1 Pro and Windows 10 Pro, and
one wireless client running Mac OSX.
This LAN is connected via an IPSEC VPN to another remote LAN with
more clients.
My issue:
When I try to connect to my Synology box using https:// from a LOCAL client, using Internet Explorer 11 or Google Chrome, everything works fine. The browsers see that the website has a valid SSL Certificate and I get no errors or warnings of any kind.
However, when I use Firefox, the certificate doesn't work at all, with the following symptoms:
For THREE Wired Clients on LAN using Windows 8.1 Pro/Windows 10 Pro and Firefox:
"The Connection is Untrusted" If I click on the little Globe next to the Address bar it says "The website does not supply identity information. Your connection to this website is not encrypted."
For Wireless Client on LAN using OSX and Firefox:
EVERYTHING WORKS FINE. If I click the lock next to the address bar in Firefox it correctly shows that the website is verified by COMODO.
For Wired Client on another LAN running Windows 7 and connecting via VPN and Firefox:
EVERYTHING WORKS FINE.
So in summary: I can connect via HTTPS using Internet Explorer or Chrome from ANYWHERE with no problems. I only have problems with FIREFOX on SPECIFIC MACHINES. It is like they aren't seeing the certificate AT ALL. What is something I could look at here?
Note that on the Windows 10 Pro machine, it is a BRAND NEW FRESH install. There is nothing else on the machine except browsers. This is a brand new fresh install of the latest Windows with the latest Firefox.
I'm going to leave this here in case someone else has the same or similar problem:
I had installed my private key and certificate on the Synology server, but had failed to include the Intermediate Certificates in the package.
Apparently, Firefox maintains a separate Certificate Store from IE and Chrome, which already come with the necessary Comodo Intermediates.
On some machines, Firefox already had the necessary Intermediates, from other sites that had provided them, but on these other machines where Firefox was rarely used, it was basically a blank slate. After installing Intermediates Certificates on the Synology server, everything was fine.
I am working on a Meteor website and conveniently, it will run on localhost with the simple command, meteor. However, I want to be able to access this website from other computers on the local network. The main reason I want to do this is for viewing and testing the app on mobile.
I am running Mac Mountain Lion 10.8, and they got rid of some of the convenient Personal Web Sharing pref panes. Everything else I have seen online deals with setting up your own server, but all I want to do is grant access from other local device...
Thanks
Find out your ip address 192.168.1.12 (mac system prefs/network)
start meteor in your project on a port (default 3000)
from another comp on network, browse 192.168.1.12:3000
Today I spent the whole day investigating why I have so many problems with WebDAV.
My Server is running Windows 2008 R2 with IIS7.5.
I created a self signed certificate and added it to the "Default Web Site". I enabled Windows Authentication and installed the WebDAV Extension.
I enabled Locking WebDAV Settings as you see here:
http://www.abload.de/img/webdavydkea.png
I then created a folder called Shares on C:\ and changed added writting permissions for the domain users.
At the end I created the Virtual Directory and set the "Authorization Rules" and the "WebDav Authorization Rules".
At the end I force the usage of SSL with the previously self signed certificate.
Now I try to connect with MAC OS X 10.7 and MAC OS X 10.6 and both mount it readonly.
If I try to mount it in Windows I get the following error message:
The mapped network drive could not be created because the following error has occurred:
A device attached to the system is not functioning.
More details if I try to mount it by using the command line:
System error 1244 has occurred.
The operation being requested was not performed because the user has not been authenticated.
If I now disable the SSL support I can mount it in Windows too including write support. MAC OS X still does only mount it as read only.
Altogether I have the following problems:
Why does MAC OS X mount the WebDAV directory as readonly even so I enabled locking support?
Why does Windows not work if I try to use SSL with the self signed certificate?
I have a similar setup, and just experienced the same "cannot connect from Windows 7" problem.
I found that I can connect from a Win XP machine. On connecting, a popup asks me if I want to trust the self-signed cert -> I accept -> it connects well.
This made me suspect that the Win 7 problem is with the cert (with not showing a popup to let me manually accept the self-signed cert). The solution to make it work is:
Either import the self-signed cert in Win 7 / IE9 into the "Trusted root CA"
cert store.
Or buy a cert that is signed by a known cert authority.