RLES Guide - Revision history

Ganskop: /* Access Outside of RLES */

2026-02-11T19:12:42Z

Access Outside of RLES

← Older revision		Revision as of 15:12, 11 February 2026
Line 39:		Line 39:
	You can request that your VM be accessible outside of RLES. To do so, send an email to gccisit@rit.edu that includes:		You can request that your VM be accessible outside of RLES. To do so, send an email to gccisit@rit.edu that includes:

	# The '''name of your VM''' (e.g. "ubuntu-1234")		# The '''name of your VM''' (e.g., "ubuntu-1234") or '''local IP address''' (e.g., 172.16.xxx.xxx)
	# What '''port(s)''' your web server is listening on (e.g. 80, 443, 3000, etc.)		# What '''port(s)''' your web server is listening on (e.g. 80, 443, 3000, etc.)
	# What '''hostname''' you want in DNS (e.g. "awesome-site", which will become "awesome-site.webdev.gccis.rit.edu")		# What '''hostname''' you want in DNS (e.g. "awesome-site", which will become "awesome-site.webdev.gccis.rit.edu")

Ganskop at 17:29, 26 February 2025

2025-02-26T17:29:23Z

← Older revision		Revision as of 13:29, 26 February 2025
Line 10:		Line 10:
	You can use VMRC to access your VMs. Download the VMRC installer for your OS:		You can use VMRC to access your VMs. Download the VMRC installer for your OS:

	* [https://~~solace~~.~~ist~~.rit.edu~~/~dmgics~~/vmrc/vmrc_windows.zip Windows]		* [https://ischool.gccis.rit.edu/vmrc/vmrc_windows.zip Windows]
	* [https://~~solace~~.~~ist~~.rit.edu~~/~dmgics~~/vmrc/vmrc_macos.dmg MacOS]		* [https://ischool.gccis.rit.edu/vmrc/vmrc_macos.dmg MacOS]
			Note that Those VMRC downloads are on the Solace web server, which is restricted to the RIT network. You just need to connect to the RIT VPN before you can download them: <nowiki>https://www.rit.edu/its/virtual-private-network-vpn</nowiki>

	===== Provisioning a VM =====		===== Provisioning a VM =====

Ganskop: /* Troubleshooting */

2025-02-05T14:16:48Z

Troubleshooting

← Older revision		Revision as of 10:16, 5 February 2025
Line 49:		Line 49:


	You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>		You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on [https://www.rit.edu/its/virtual-private-network-vpn the RIT network] to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>

	====Group Work====		====Group Work====
Line 59:		Line 59:
	'''Freezing'''<br>If your VM appears to freeze, try exiting VMRC or your host computer's browser tab, and then reconnect to the VM.		'''Freezing'''<br>If your VM appears to freeze, try exiting VMRC or your host computer's browser tab, and then reconnect to the VM.

	'''No VM access outside of RLES'''<br>If you've followed above for "Access Outside of RLES", and you're still not able to access your VM outside of RLES, try these steps:		'''No VM access outside of RLES'''<br>If you've followed the steps above for "[[RLES Guide#Access Outside of RLES\|Access Outside of RLES]]", and you're still not able to access your VM outside of RLES, try these steps:

	# First, make sure that you're able to access your application inside the VM on localhost (and specify the port). E.g., <nowiki>http://localhost:3000</nowiki>. If you can't access your app on localhost, then you've got something wrong with how you're serving your app - you need to look at your server code or web server.		# First, make sure that you're able to access your application inside the VM on localhost (and specify the port). E.g., <nowiki>http://localhost:3000</nowiki>. If you can't access your app on localhost, then you've got something wrong with how you're serving your app - you need to look at your server code or web server.

Ganskop at 14:10, 5 February 2025

2025-02-05T14:10:05Z

← Older revision		Revision as of 10:10, 5 February 2025
Line 47:		Line 47:

	Once the setup is complete, you'll be able to access your site from any browser outside of RLES at:<blockquote>https://[hostname].webdev.gccis.rit.edu</blockquote>Note that a TLS certificate is automatically added by the RLES reverse proxy, so you'll access your site over HTTPS even though you haven't configured your web server for it, and port 443 will be mapped to the port that your web server is listening on. That means that if you can access your site on your VM at "<nowiki>http://localhost:3000</nowiki>" and "<nowiki>http://172.16.0.1:3000</nowiki>", and 172.16.0.1 has been mapped in the proxy to awesome-site.webdev.gccis.rit.edu, you would access your site outside of RLES at "<nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>" (note the 's' in 'https' and that no port is specified).		Once the setup is complete, you'll be able to access your site from any browser outside of RLES at:<blockquote>https://[hostname].webdev.gccis.rit.edu</blockquote>Note that a TLS certificate is automatically added by the RLES reverse proxy, so you'll access your site over HTTPS even though you haven't configured your web server for it, and port 443 will be mapped to the port that your web server is listening on. That means that if you can access your site on your VM at "<nowiki>http://localhost:3000</nowiki>" and "<nowiki>http://172.16.0.1:3000</nowiki>", and 172.16.0.1 has been mapped in the proxy to awesome-site.webdev.gccis.rit.edu, you would access your site outside of RLES at "<nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>" (note the 's' in 'https' and that no port is specified).


	You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>		You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>

Ganskop at 14:08, 5 February 2025

2025-02-05T14:08:01Z

← Older revision		Revision as of 10:08, 5 February 2025
Line 47:		Line 47:

	Once the setup is complete, you'll be able to access your site from any browser outside of RLES at:<blockquote>https://[hostname].webdev.gccis.rit.edu</blockquote>Note that a TLS certificate is automatically added by the RLES reverse proxy, so you'll access your site over HTTPS even though you haven't configured your web server for it, and port 443 will be mapped to the port that your web server is listening on. That means that if you can access your site on your VM at "<nowiki>http://localhost:3000</nowiki>" and "<nowiki>http://172.16.0.1:3000</nowiki>", and 172.16.0.1 has been mapped in the proxy to awesome-site.webdev.gccis.rit.edu, you would access your site outside of RLES at "<nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>" (note the 's' in 'https' and that no port is specified).		Once the setup is complete, you'll be able to access your site from any browser outside of RLES at:<blockquote>https://[hostname].webdev.gccis.rit.edu</blockquote>Note that a TLS certificate is automatically added by the RLES reverse proxy, so you'll access your site over HTTPS even though you haven't configured your web server for it, and port 443 will be mapped to the port that your web server is listening on. That means that if you can access your site on your VM at "<nowiki>http://localhost:3000</nowiki>" and "<nowiki>http://172.16.0.1:3000</nowiki>", and 172.16.0.1 has been mapped in the proxy to awesome-site.webdev.gccis.rit.edu, you would access your site outside of RLES at "<nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>" (note the 's' in 'https' and that no port is specified).

	You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>		You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>

Ganskop: Added information for configuring VMs for access outside of RLES

2025-02-05T14:07:32Z

Added information for configuring VMs for access outside of RLES

← Older revision		Revision as of 10:07, 5 February 2025
Line 42:		Line 42:
	# What '''hostname''' you want in DNS (e.g. "awesome-site", which will become "awesome-site.webdev.gccis.rit.edu")		# What '''hostname''' you want in DNS (e.g. "awesome-site", which will become "awesome-site.webdev.gccis.rit.edu")

	Once the ~~setup is complete~~, you'll be ~~able~~ to ~~access~~ your ~~site from any browser outside of RLES at:<blockquote>https://[hostname]~~.~~webdev~~.~~gccis~~.~~rit~~.~~edu</blockquote>Note that a TLS certificate is automatically added by the RLES proxy~~, so ~~you'll access your site over HTTPS even though you haven't configured your web server for it.~~		Once an entry has been made in the RLES reverse proxy, you'll be assigned an IP address that is mapped to your DNS name. Set that static IP address on your VM, and set the subnet mask to 255.255.254.0 and gateway to 172.16.1.254, like so:

			[[File:Static IP settings.png\|alt=Static IP settings\|400x400px]]

			Once the setup is complete, you'll be able to access your site from any browser outside of RLES at:<blockquote>https://[hostname].webdev.gccis.rit.edu</blockquote>Note that a TLS certificate is automatically added by the RLES reverse proxy, so you'll access your site over HTTPS even though you haven't configured your web server for it, and port 443 will be mapped to the port that your web server is listening on. That means that if you can access your site on your VM at "<nowiki>http://localhost:3000</nowiki>" and "<nowiki>http://172.16.0.1:3000</nowiki>", and 172.16.0.1 has been mapped in the proxy to awesome-site.webdev.gccis.rit.edu, you would access your site outside of RLES at "<nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>" (note the 's' in 'https' and that no port is specified).
	You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>		You can SSH into your VM too (as long as SSH is enabled on the VM), but you must be on the RIT network to do so (note that there'll be a custom port for each VM):<blockquote>ssh [username]@[hostname].webdev.gccis.rit.edu -p[port]</blockquote>

	==== Group Work====		====Group Work====
	You should all be able to see your groups VMs; if, on the Deployments page, you don't see a VM that someone else in your group created, click the filter icon next to "Deployments" and clear the checkmark next to your name.		You should all be able to see your groups VMs; if, on the Deployments page, you don't see a VM that someone else in your group created, click the filter icon next to "Deployments" and clear the checkmark next to your name.

	==== Troubleshooting ====		====Troubleshooting====
	'''VM loses connectivity'''<br>If your VM loses connectivity, try toggling the wired connection: Click the power icon in the top right corner, click "Wired Connected", and click "Turn Off". Then again click the power icon, click "Wired Off", and then "Connect".		'''VM loses connectivity'''<br>If your VM loses connectivity, try toggling the wired connection: Click the power icon in the top right corner, click "Wired Connected", and click "Turn Off". Then again click the power icon, click "Wired Off", and then "Connect".

	'''Freezing'''<br>If your VM appears to freeze, try exiting VMRC or your host computer's browser tab, and then reconnect to the VM.		'''Freezing'''<br>If your VM appears to freeze, try exiting VMRC or your host computer's browser tab, and then reconnect to the VM.

			'''No VM access outside of RLES'''<br>If you've followed above for "Access Outside of RLES", and you're still not able to access your VM outside of RLES, try these steps:

			# First, make sure that you're able to access your application inside the VM on localhost (and specify the port). E.g., <nowiki>http://localhost:3000</nowiki>. If you can't access your app on localhost, then you've got something wrong with how you're serving your app - you need to look at your server code or web server.
			# Still inside the VM, make sure that you can access your application on the assigned IP address (with the specified port. E.g., <nowiki>http://172.16.0.1:3000</nowiki>. If you can't access your app on the assigned VM, then you probably have the network settings misconfigured. Check out the steps above, under "Access Outside of RLES", for setting a manual IP address.
			# Once you've confirmed that you can access your app by IP on your VM, ensure that you can access it on other VMs in RLES. Spin up another VM and try to access your app on the specified IP and port. If your app won't load, then you probably have a firewall issue on your app's VM.
			# Finally, test out accessing your app outside of RLES by using the assigned DNS name, e.g., <nowiki>https://awesome-site.webdev.gccis.rit.edu</nowiki>. Do ''not'' specify a port. If you can access your app inside RLES but not outside, then there's probably a configuration issue in the reverse proxy, and you should email gccisit@rit.edu.

Ganskop: /* Access Outside of RLES [only for Old RLES] */

2025-02-03T17:16:44Z

Access Outside of RLES [only for Old RLES]

← Older revision		Revision as of 13:16, 3 February 2025
Line 35:		Line 35:
	To use VMware's Remote Console, click "Connect using VMRC" (see above for links to the VRMC download). A new browser tab will open with a link for connecting to the VM. Click the "Connect to console using VMRC" to open your VM using the VMRC application.		To use VMware's Remote Console, click "Connect using VMRC" (see above for links to the VRMC download). A new browser tab will open with a link for connecting to the VM. Click the "Connect to console using VMRC" to open your VM using the VMRC application.

	==== Access Outside of RLES ~~[only for Old RLES]~~ ====		==== Access Outside of RLES ====
	You can request that your VM be accessible outside of RLES. To do so, send an email to gccisit@rit.edu that includes:		You can request that your VM be accessible outside of RLES. To do so, send an email to gccisit@rit.edu that includes:

Ganskop: /* Accessing a VM */

2025-02-03T17:16:29Z

Accessing a VM

← Older revision		Revision as of 13:16, 3 February 2025
Line 29:		Line 29:
	RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.		RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.

	Once a VM is powered on, click the VM's name (not the network), and then click the "Actions" (gear) dropdown to see available options (see image at right.		Once a VM is powered on, click the VM's name (not the network), and then click the "Actions" (gear) dropdown to see available options (see image at right).

	To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.		To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.

Ganskop: /* Accessing a VM */

2025-02-03T17:16:15Z

Accessing a VM

← Older revision		Revision as of 13:16, 3 February 2025
Line 28:		Line 28:
	[[File:RLES test deployment.png\|right\|450x450px\|RLES test deployment]]		[[File:RLES test deployment.png\|right\|450x450px\|RLES test deployment]]
	RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.		RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.

	Once a VM is powered on, click the VM's name (not the network), and then click the "Actions" (gear) dropdown to see available options (see image at right.		Once a VM is powered on, click the VM's name (not the network), and then click the "Actions" (gear) dropdown to see available options (see image at right.

	To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.		To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.

Ganskop: Add screenshot

2025-02-03T17:15:49Z

Add screenshot

← Older revision		Revision as of 13:15, 3 February 2025
Line 26:		Line 26:
	===== Accessing a VM =====		===== Accessing a VM =====
	RLES VMs are, by default, only accessible within RLES. To access a VM that you've provisioned, go to the "Deployments" tab and find the entry for the VM that you're looking for.		RLES VMs are, by default, only accessible within RLES. To access a VM that you've provisioned, go to the "Deployments" tab and find the entry for the VM that you're looking for.
			[[File:RLES test deployment.png\|right\|450x450px\|RLES test deployment]]
	RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.		RLES VMs typically automatically suspend after 6 hours in order to conserve RLES resources, so if the status of your VM is "Off", click the "Actions" dropdown (on the top right) and choose "Power on deployment" (then click "Submit" on the next screen). It should take a minute or so for the VM to turn back on.
	~~[[File:RLES actions menu.png\|alt=RLES VM context menu\|thumb\|502x502px\|RLES VM context menu]]~~		Once a VM is powered on, click the VM's name (not the network), and then click the "Actions" (gear) dropdown to see available options (see image at right.
	Once a VM is powered on, click the VM's name, and then ~~in the panel on the right,~~ click the "Actions" (gear) dropdown to see available options.

	To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.		To access a VM, you can use a browser, or you can use VMware's Remote Console (VMRC). Using a browser to access the VM is quick and easy, but it won't allow for copy/pasting from your host computer. To use the browser, click "Connect to Remote Console" in the context menu.