# How to change umbrel.local to something else? **URL:** \ **Category:** General Discussion\ **Created:** [November 15, 2021, 11:12am UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694 "2021-11-15T11:12:29Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![Guillaume](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guillaume](https://community.umbrel.com/u/Guillaume)\ **Post date:** [December 27, 2021, 12:11pm UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/21 "2021-12-27T12:11:15Z")
thanks @DarthCoin but modifying my local hosts file is a workaround not a solution. as far as I can tell, umbrel does not work with multiple node on the same network. ---
**Author:** ![DarthCoin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/darthcoin/32/1628_2.png) [@DarthCoin](https://community.umbrel.com/u/DarthCoin)\ **Post date:** [December 27, 2021, 12:24pm UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/22 "2021-12-27T12:24:43Z")
worked for me, exactly as I just explained to you. If you have a local DNS server, you can set whatever names in your .local domain for each device/IP. If you do not have a local DNS server, then the best way and eeasy is to edit your local hosts file. Changing the umbrel code just for that will make things worst than you can imagine. But if you really want to fuck around with your umbrel, go ahead. But don’t come back and complain or cry that your node is no longer working. ---
**Author:** ![Guillaume](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guillaume](https://community.umbrel.com/u/Guillaume)\ **Post date:** [December 27, 2021, 1:41pm UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/23 "2021-12-27T13:41:02Z")
Thanks for trying to help @DarthCoin 🙏 Running a local DNS server doesn’t affect having the CORS error on login. here is a quick list of existing github issues from different users experiencing same issue on that specific topic > > > Hello, > > I've performed a fresh install of Umbrel 0.4.2 onto an Ubuntu 20 publi…c server. > > All went OK until the message "Error - Not allowed by CORS". > > There are related issues reported, for example: > https://github.com/getumbrel/umbrel-os/issues/63 > https://github.com/getumbrel/umbrel/issues/669 > https://github.com/getumbrel/umbrel/issues/584 > https://github.com/getumbrel/umbrel/issues/398 > > However, the issue remains on a fresh install. > > At first the problem was using the public IP address, which for some odd reason was not accepted. > Then I've pointed a domain to the IP address, same result. > Finally started editing the "start" script. It was not enough to just add the domain, also had to hardcode the custom port number. > > After hardcoding the domain name and port number on \`DEVICE\_HOSTS\` it has worked as intended. > > I've solved my issue, but would be nice to include this information on the installation page to help others. > Thanks. > > > For easier demoing to others I decided to host umbrel on a vps. > The vps itsel…f is managed by plesk and is running centos. > > I managed to setup and sucessfully run umbrel. I also connected to it via public address (umbrel.payserver.org) > When trying to login with a password I get the following error: > > \`\`\` > umbrel-manager > Not allowed by CORS > /v1/account/login > Error: Not allowed by CORS > at origin (/app/middlewares/cors.js:14:23) > at /app/node\_modules/cors/lib/index.js:219:13 > at optionsCallback (/app/node\_modules/cors/lib/index.js:199:9) > at corsMiddleware (/app/node\_modules/cors/lib/index.js:204:7) > at Layer.handle \[as handle\_request\] (/app/node\_modules/express/lib/router/layer.js:95:5) > at trim\_prefix (/app/node\_modules/express/lib/router/index.js:317:13) > at /app/node\_modules/express/lib/router/index.js:284:7 > at Function.process\_params (/app/node\_modules/express/lib/router/index.js:335:12) > at next (/app/node\_modules/express/lib/router/index.js:275:10) > at expressInit (/app/node\_modules/express/lib/middleware/init.js:40:5) > \`\`\` > > > I tried using > \`\`\`sh > sudo NGINX\_PORT=8000 ./scripts/start > \`\`\` > But got a snac…kbar error "Not allowed by CORS". > > My fix was changing "scripts/start" from: > \`\`\`sh > DEVICE\_IP="$(ip -o route get to 8.8.8.8 | sed -n 's/.\*src \\(\[0-9.\]\\+\\).\*/\\1/p')" > \`\`\` > to this > \`\`\`sh > DEVICE\_IP="$(ip -o route get to 8.8.8.8 | sed -n 's/.\*src \\(\[0-9.\]\\+\\).\*/\\1/p'):$NGINX\_PORT" > \`\`\` > > > I'm trying to install Umbrel (manually, not the Umbrel image) on Raspbian Lite 6…4-bit. Everything starts up as expected but during registration it always fails with "Not allowed by CORS". > > !\[image\](https://user-images.githubusercontent.com/1210628/112490190-73514100-8d7f-11eb-9ab0-7ab0799f7db9.png) > > !\[Screenshot 2021-03-25 at 15 32 43\](https://user-images.githubusercontent.com/1210628/112490144-6af90600-8d7f-11eb-986b-a17c64c4bc14.jpg) > > > I have discovered what I believe to be a bug in 4.9 especially regarding 2fa. > I… have two nodes that I'm trying to run on one LAN. Both are running 4.9. 2FA \_is not\_ enabled > > \*\*Symptom/recreate:\*\* > One LN node running on a LAN > Boot a second LN Node. > The Second Node (automatically named umbel-2) is accessible from a browser. Using the user interface (umbrel-2.local), it accepts the password then goes directly to the 2fa prompt and a message comes up stating that CORS is not allowed. > > \*\*Configuration:\*\* > Both nodes have been previously configured and set up they run fine when only one is on the network. Each worked independently. > Raspberry PI 4, 4G, 32G sim, Umbrel 0.4.9, 1T Crucial SSD, PI power supplies, USB 3.1 cables. > > \*\*Notes:\*\* > It looks like the umbrel nodes don't play well with each other. > I suspect that there is something hardcoded in the startup that makes the node think it's the only one and doesn't allow for a second or third one on the LAN. > The "CORS" error and the fact that the 2nd node goes directly to 2fa verification indicates that the designer didn't take into account the possibility of more than one node existing on the LAN. > > Can someone give this a try and confirm/deny? I'm stuck unless I set up VLANs for each node. I'm not a fan of tweaking the router just to accommodate a misbehaving node. > > Thanks in the last issue @lukechilds propose to modify /etc/hostname but it doesn’t solve the issue… ---
**Author:** ![dar1LN](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@dar1LN](https://community.umbrel.com/u/dar1LN)\ **Post date:** [December 27, 2021, 9:25pm UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/24 "2021-12-27T21:25:57Z")
I was having the same problem. I found a post from Tom’s hardware, [https://www.tomshardware.com/how-to/raspberry-pi-change-hostname](https://www.tomshardware.com/how-to/raspberry-pi-change-hostname) , However, You can change the hostname on each of the umbrel devices, then you won’t get that stupid CORS error. The raspi-config is the equivalent of your PC’s BIOS setup. There are several options for customizations. One of them is the hostname. use that link from Tom’s Hardware. It’s real clear. ---
**Author:** ![Hakuna](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/hakuna/32/549_2.png) [@Hakuna](https://community.umbrel.com/u/Hakuna)\ **Post date:** [December 28, 2021, 10:44am UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/25 "2021-12-28T10:44:31Z")
Status: I’m getting closer to the root cause of why umbrel’s changing the host-name, even though there is no second umbrel on the network: A bug of avahi-daemon handling IPv6 and IPv4 at the same time [Github Issue](https://github.com/lathiat/avahi/issues/117) ``` umbrel@umbrel:~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-12-26 11:41:19 CET; 1 day 23h ago Main PID: 375 (avahi-daemon) Status: "avahi-daemon 0.7 starting up." Tasks: 2 (limit: 4915) CGroup: /system.slice/avahi-daemon.service ├─375 avahi-daemon: running [umbrel-2.local] └─394 avahi-daemon: chroot helper ``` I’m digging deeper if there is any other mitigation but disabling IPv6 handling for avahi. Will report back here. @DarthCoin and @Guillaume as FYI ---
**Author:** ![carterjoshua603](https://avatars.discourse-cdn.com/v4/letter/c/c57346/32.png) [@carterjoshua603](https://community.umbrel.com/u/carterjoshua603)\ **Post date:** [January 20, 2023, 2:04am UTC](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694/26 "2023-01-20T02:04:55Z")
@dar1LN Gave me the right idea for accomplishing this. In my case, I had Ubuntu installed on a Rock PI 4B and had installed Umbrel via the curl command, and it used my device’s hostname: rockpi4b.local by default. Chaning my device’s hostname via: ```bash vim /etc/hostname ``` and restarting the device did the trick. Initially, I received the same CORS error reported above, but stopping/starting Umbrel (via `~/umbrel/scripts/` seemed to resolve that. [Previous page](https://community.umbrel.com/t/how-to-change-umbrel-local-to-something-else/4694.md?page=1)