Comments (13)
sudo tail -30 /var/log/nginx/error.log
from remotely.
Didn't mean to close it.
from remotely.
It looks like the Nginx configuration was set up with "remotely.example.com" as the host name. The host name needs to be an actual URL/IP that points to the machine/VM, or the connection will be rejected.
This is true for any Nginx server that wants to host multiple sites on one machine (not just a Remotely thing). Since I don't know ahead of time if you intend to host multiple sites, it's configured to only accept traffic for a specific host name. You can manually change the Nginx configuration to "catch all" if you'd prefer that.
from remotely.
I whitelisted the private info.... Sorry I should of specified.
from remotely.
Let me give you a better description.
I deployed a brand new install of Ubuntu of 18.04
Downloaded and unzipped the repo
Ran the Remotely_Server_Install.sh with sudo.
Followed the prompts
script finished and I went to domain remote.example.com < protecting my domain by not posting it....
502 Gateway error
from remotely.
Sorry for the misunderstanding. I get a lot of emails where people literally enter "example.com," so I just assumed. My bad.
I just tested deploying on a fresh VM, and all went smoothly. Could you try checking the output of the following?
nginx -t
systemctl status remotely
wget --spider localhost:5000 (unless port was changed)
What are the results of those?
from remotely.
remotely@remotely:~$ sudo nginx -t
[sudo] password for remotely:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
remotely@remotely:~$ systemctl status remotely
● remotely.service - Remotely Server
Loaded: error (Reason: Exec format error)
Active: inactive (dead)
Jun 27 06:56:12 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:13 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:54 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:54 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:56 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:57 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
Jun 27 06:56:57 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path
lines 1-14/14 (END)
● remotely.service - Remotely Server
Loaded: error (Reason: Exec format error)
Active: inactive (dead)
Jun 27 06:56:12 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:13 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:14 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:54 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:54 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:56 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:57 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
Jun 27 06:56:57 remotely systemd[1]: /etc/systemd/system/remotely.service:5: Working directory path '' is not absolute.
remotely@remotely:~$ wget --spider localhost:5000
Spider mode enabled. Check if remote file exists.
--2019-06-27 19:59:53-- http://localhost:5000/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:5000... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:5000... failed: Connection refused.
remotely@remotely:~$ wget --spider localhost:80
Spider mode enabled. Check if remote file exists.
--2019-06-27 20:00:02-- http://localhost/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 612 [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
remotely@remotely:~$ wget --spider localhost:443
Spider mode enabled. Check if remote file exists.
--2019-06-27 20:00:09-- http://localhost:443/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:443... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
Remote file does not exist -- broken link!!!
from remotely.
It looks like the service isn't starting because the WorkingDirectory is blank (which means ExecStart is likely incorrect as well).
The first prompt of the install script asks for the root path where the app is installed (i.e. where the Remotely_Server.dll is located). I might want to make the prompt a little more clear. It sets it in the service file like so:
[Service]
WorkingDirectory=$appRoot
ExecStart=/usr/bin/dotnet $appRoot/Remotely_Server.dll
Check your service config (/etc/systemd/system/remotely.service) and make sure those values have the absolute path in them. Let me know if that was it. :)
from remotely.
Actually, looking at this again, that variable is used for several other commands. You might just want to run the script again if that variable was indeed blank.
from remotely.
Here is a video of what I am doing during the re-run of the script. This link expires in 1 day. We aren't using this in production or anything. Its for my homelab I just work from home so it was easier to send it this way.
from remotely.
When it's asking for the app path, it looks like you're entering an empty string. It's expecting the absolute path to where you want to install the app/website. See here: https://lucency.co/ImageShare/?view=lvwjryji1p2
That path is stored in a variable and used throughout the rest of the script.
from remotely.
10/10 User error. Works now! Thanks! I thought when it mentioned "typically /var..." that was the default and if you wanted something different please enter it now. Bad on me for making the assumption.
from remotely.
No problem!
Now that you mention it, I think someone else gave me similar feedback once.
I added that as the "default" location, so it behaves you described above. Thanks!
from remotely.
Related Issues (20)
- High CPU, RAM and I/O usage HOT 15
- How to build HOT 1
- add certificate in remotly step by step HOT 2
- Turn off auto-update the agent on Windows HOT 1
- FEATURE REQUEST: Record the remote screen HOT 1
- Device ID is missing. Cant use Get support ! HOT 2
- How to update? look like everything has changed... HOT 2
- SSO OAUTH HOT 3
- Add More Modern TLS Support for Install-Remotely.ps1 HOT 1
- Migration from older Remotely Version to the newest one failed how to migrate DB and get login working again HOT 1
- ListView for the Home Screen HOT 4
- Docker: ResetPassword link uses wrong hostname HOT 1
- can't connect if i rename the exe HOT 2
- What's with Docker Tags? HOT 3
- Linux client installation issues. HOT 1
- Cannot Start Remote Control Session -- Manjaro KDE HOT 2
- Remotely wont run in aarch64?
- Feature Request: Software Install Component using winget or choco HOT 4
- Numlock is not writing numbers
- New install of remotely via Docker is no-go HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from remotely.