Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accepting Asset Assignment from Public Internet #8384

Open
aaronhill1980 opened this issue Aug 28, 2020 · 6 comments
Open

Accepting Asset Assignment from Public Internet #8384

aaronhill1980 opened this issue Aug 28, 2020 · 6 comments
Assignees
Labels

Comments

@aaronhill1980
Copy link

Hi all,

Just to summarize Snipe IT is setup completely and working fine.
Users / staff get the email as well to accept the asset.

Problem is I dont know if there is a way when the staff member replies back to the email to accept from outside of the domain for it to not error stating it cant load the page. This is because the SNIPE-IT server is on the local IP subnet i.e. https://192.168.0.* and clearly replying to that from the outside internet will not work.

I understand (as an IT Manager) what needs to happen but I am not sure it SNIPE IT allows for it.

Has anyone achieved this via port forwarding the traffic or does snipeit allow external access into the server its installed

Sorry If i didnt follow the rules or if this is not something you can help with, just thought I would try.

Thanks
Aaron

@snipe
Copy link
Owner

snipe commented Aug 29, 2020

That's more of a networking/DNS issue than an issue specific to Snipe-IT.

Leaving this open in case someone has some clever workarounds, but IMHO this would just be easier by setting it up so that it's accessible through the Internet versus private network.

@aaronhill1980
Copy link
Author

Thanks for that appreciate it.

I mean it is easy to make it accessible from the internet but the issue is when a user receives the email to there inbox it appears to be hard coded in Snipe email to send it back to the internal IP Address which isnt accessible from the outside world. Is there a way to change this hard coded IP that the email presents when you click the button in the email to send it back to the WAN IP of the server ?

@tom-sin
Copy link

tom-sin commented Aug 31, 2020

Hi,

you need a public DNS entry which resolve to your public ip. Set public DNS entry same as your private DNS entry.
Like:
snipe-it.aaronhill.de --> 192.168.0.1 thats your private DNS entry
snipe-it.aaronhill.de --> 10.10.10.1 thats your external DNS entry

also you can work with CNAMES (DNS Alias).

@aaronhill1980
Copy link
Author

Hi,

you need a public DNS entry which resolve to your public ip. Set public DNS entry same as your private DNS entry.
Like:
snipe-it.aaronhill.de --> 192.168.0.1 thats your private DNS entry
snipe-it.aaronhill.de --> 10.10.10.1 thats your external DNS entry

also you can work with CNAMES (DNS Alias).

Will give it a go is there a specific port that needs to forward from the main gateway / firewall to this server for it to resolve?

@aaronhill1980
Copy link
Author

Hi,

you need a public DNS entry which resolve to your public ip. Set public DNS entry same as your private DNS entry.
Like:
snipe-it.aaronhill.de --> 192.168.0.1 thats your private DNS entry
snipe-it.aaronhill.de --> 10.10.10.1 thats your external DNS entry

also you can work with CNAMES (DNS Alias).

Hi mate,
Ok so i setup the Public DNS Entry to pass traffic from the domain to the Public WAN IP of where the Snipe IT Server resides and also in Windows DNS Server I setup the DNS Entry to pass traffic as you mentioned. Just waiting on DNS Propagation.

Is there any other forwards on the firewall I need to do in order for the reply from the Public internet to resolve the Internal Snipe IT Server ?

@stale
Copy link

stale bot commented Dec 25, 2020

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

@stale stale bot added the stale label Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants